Eric,
Do you mean PING with multicast and broadcast? Please elaborate. The case for ATTACH is demonstrated in section 11.
--Michael
-------- Original Message --------
Subject: Re: [P2PSIP] Section 1.2 Architecture is incomplete
From: Eric Rescorla <[email protected]>
Date: Sun, March 07, 2010 11:43 am
To: Michael Chen <[email protected]>
Cc: "[email protected]" <[email protected]>
I had thought we got rid of those since they are underapecified. If not we should.Hi,For the base draft, at least two messages are sent without TLS/DTLS: ATTACH and PING (multi-cast or broadcast use case). The two diagrams in section 1.2 should reflect these two usages.Also, to be clear and explicit, the overlay link layer should depict the frame header and its relation to TLS/DTLS. I suggest the following:-------------------------------------- Overlay Link API
+------+ +------+ +------+
|<none>| |TLS | |DTLS | ...
+------+ +------+ +------+
+---------------------------------+| Framing Header |+---------------------------------+The <none> box accounts for the ATTACH and PING without TLS/DTLS.Thanks--Michael_______________________________________________
P2PSIP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/p2psip
_______________________________________________ P2PSIP mailing list [email protected] https://www.ietf.org/mailman/listinfo/p2psip
