Draft: draft-ietf-perc-dtls-tunnel

Commentary: Draft -08
Paragraph (version A):
An objective of Privacy-Enhanced RTP Conferencing (PERC) RFC8871 is
to ensure that endpoints in a multimedia conference have access to
the end-to-end (E2E) and hop-by-hop (HBH) keying material used to
encrypt and authenticate Real-time Transport Protocol (RTP) RFC3550
packets, while the Media Distributor has access only to the hop-by-
hop (HBH) keying material for encryption and authentication.
Paragraph (version B):
An objective of Privacy-Enhanced RTP Conferencing (PERC) RFC8871 is
to ensure that endpoints in a multimedia conference have access to
the end-to-end (E2E) and hop-by-hop (HBH) keying material used to
encrypt and authenticate Real-time Transport Protocol (RTP) RFC3550
packets, while the Media Distributor has access only to the HBH
keying material for encryption and authentication.
Paragraph (version A):
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC2119 when they
appear in ALL CAPS.  These words may also appear in this document in
lower case as plain English words, absent their normative meanings.
Paragraph (version B):
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 RFC2119 RFC8174 when, and only when, they appear in all capitals,
as shown here.
Paragraph (version A):
message when the TLS tunnel is initially established.  The key
distributor will use that information to select a common profile
supported by both the endpoint and the media distributor to ensure
that hop-by-hop operations can be successfully performed.
Paragraph (version B):
message when the TLS tunnel is initially established.  The key
distributor will use that information to select a common profile
supported by both the endpoint and the media distributor to ensure
that HBH operations can be successfully performed.
Paragraph (version A):
message when received and use it for hop-by-hop encryption and
authentication.
Paragraph (version B):
message when received and use it for HBH encryption and
authentication.
Paragraph (version A):
The media distributor MUST assign a unique association identifier for
each endpoint-initiated DTLS association and include it in all
messages forwarded to the key distributor.  The key distributor will
subsequently include this identifier in all messages it sends so that
the media distributor can map messages received via a tunnel and
forward those messages to the correct endpoint.  The association
identifier MUST be randomly assigned UUID RFC4122 value.
Paragraph (version B):
The media distributor MUST assign a unique association identifier for
each endpoint-initiated DTLS association and include it in all
messages forwarded to the key distributor.  The key distributor will
subsequently include this identifier in all messages it sends so that
the media distributor can map messages received via a tunnel and
forward those messages to the correct endpoint.  The association
identifier MUST be randomly assigned UUID value as described
Section 4.4 of RFC4122.
Paragraph (version A):
message with the corresponding values received from the SDP
transmitted by the endpoint.  It is through this correlation that the
key distributor can be sure to deliver the correct conference key to
the endpoint.
Paragraph (version B):
message with the values received from the SDP transmitted by the
endpoint.  It is through this process that the key distributor can be
sure to deliver the correct conference key to the endpoint.
Paragraph (version B):
The procedures for updating this table are those defined as "IETF
Review" in section 4.8 if [!@RFC8126].