On Mar 7, 2010, at 11:49, "Michael Chen" <[email protected]>
wrote:
Eric,
Do you mean PING with multicast and broadcast? Please elaborate.
Yes. I'm not sure it's fully specified
The case for ATTACH is demonstrated in section 11.
I don't see that. Afaict all the examples in s 11 are compatible with
tls. Which one do you think is not?
Ekr
--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.
Ekr
On Mar 7, 2010, at 11:28, "Michael Chen" <[email protected]>
wrote:
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
