-----Original Message-----
From: Melinda Shore [mailto:melinda(_dot_)shore(_at_)gmail(_dot_)com]
Sent: Sunday, March 22, 2009 12:44 PM
To: Dan Wing
Cc: 'Joel Jaeggli'; 'IAB'; 'IETF Discussion Mailing List'
Subject: Re: Comment on draft-iab-ipv6-nat-00
Dan Wing wrote:
ICE does not perform resource reservation and ICE does not
perform capability negotiation.
You might not call it that but it does, in fact,
snag resources.
ICE sends UDP packets and TCP packets. I agree they might
create state in a NAT, and state in a NAT is a resource. But
with that argument my web browser is also doing 'resource
reservation'.
On the capability negotiation
front I figure that's just a matter of time.
(Somebody needs to come up with a cool acronym
expansion for METASTASIS).
Sure. But every exensible protocol can do 'capability
negotiation'. TCP does it: winscale, timestamps, and SACK
are all capabilities that are negotiated during connection
establishment.
-d
That said, I'm not crazy about capability negotiation.
Try something and send meaningful error messages if
it doesn't work. Avoid race conditions and try to
keep state machines cleaner.
Melinda
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf