Comments (10)
We should check terminology alignment with RFC 8446 and RFC 4895 as well
- I removed some "-" to align with RFC 4895 but there might be more
- RFC 8446 use ClientHello and KeyUpdate when it talks about the exact name of the message but use Client Hello and key update in other parts.
from draft-westerlund-tsvwg-dtls-over-sctp-bis.
ClientHello is a name and Client Hello is a noun. I will check for such cases
from draft-westerlund-tsvwg-dtls-over-sctp-bis.
Also I noted that rfc4895 is not aligned with rfc9260 when using INIT-ACK, COOKIE-ECHO etc.
from draft-westerlund-tsvwg-dtls-over-sctp-bis.
Lets follow RFC 9260 usage as that is the latest spec and current main spec.
from draft-westerlund-tsvwg-dtls-over-sctp-bis.
Let's check for alignment with RFC 4895 as well. The term "key-id" is used in one place.
from draft-westerlund-tsvwg-dtls-over-sctp-bis.
key-id --> Key Identifier
done
from draft-westerlund-tsvwg-dtls-over-sctp-bis.
There's no SCTP-AUTH in 4895, I replace with SCTP AUTH instead that is locally defined.
from draft-westerlund-tsvwg-dtls-over-sctp-bis.
RFC 9260 talks about SCTP-AUTH .....
The SCTP Authentication extension SCTP-AUTH [RFC4895]
from draft-westerlund-tsvwg-dtls-over-sctp-bis.
RFC 9260 talks about SCTP-AUTH .....
The SCTP Authentication extension SCTP-AUTH [RFC4895]
I think actually using SCTP-AUTH would be clearer and I think that is fine if RFC 9260 is using it. Should we revert this change?
from draft-westerlund-tsvwg-dtls-over-sctp-bis.
OK, even though rfc4895 uses SCTP AUTH.
RFC9260 has higher prio
from draft-westerlund-tsvwg-dtls-over-sctp-bis.
Related Issues (20)
- Define how the SCTP-AUTH keys are derived HOT 5
- Don't reuse the RFC 6803 exporter label HOT 1
- EC(DHE) -> (EC)DHE HOT 1
- Resumption performance HOT 3
- Cryptographic considerations is very long HOT 1
- How do you limit new connections HOT 1
- Mandatory mutual authentication HOT 3
- Use RFC 7525(bis) HOT 3
- Authenticating fallback to RFC 6083 HOT 6
- DTLS 1.3 Only
- Editorial alignment in style of the IANA sub sections needed HOT 1
- DTLS considerations need to be clear that AEAD limits MUST be handled by new connection
- Address new vulnerabilities found in SCTP-AUTH HOT 10
- DTLS Considerations for Handling of Endpoint Pair Shared Secrets HOT 5
- Clarify that COOKIE-ECHO and COOKIE-ACK are not authenticated
- Create DTLS/SCTP Control Message IANA registry
- Update solution properties description
- Add text on how SCTP restart works
- Overstated Security Properties
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from draft-westerlund-tsvwg-dtls-over-sctp-bis.