Re: [Ietf-behave] p2p-state as new milestone?
Speaking only for myself...
Dan,
Let me clarify on the applicability of the p2p-state draft to the WG. The
document provides the current state of NAT traversal techniques in use by
P2P
applications. As such, this provides a background for the recommendations
in
draft-ford-behave-app-04.txt, which is currently a candidate for the
"protocol
design techniques for using the existing set of NAT traversal approaches"
milestone. For this reason, I requested for the p2p-state draft to be
advanced
as informational RFC.
My read of the charer for this WG is that it is focussed on requirements
and
BCP documents. So, initialy (a few months ago), I requested Magnus to
review
this as independent submission, to which he readily agreed. The doucment
was
sent for review on both behve and p2psip lists. The current rev of the
draft
folds in all the comments received during that review. Later, Magnus
clarified
that he believed that the draft indeed is within the WG charter and as
such
should be progressed as WG document. Hence my request to consider this as
WG
draft. I understand, you are aware of the events preceding the request.
But, I
am sending this note for the benefit of the WG at large.
At the P2PSIP ad hoc in Montreal, my understanding was that the proposed
P2PSIP charter points to BEHAVE for NAT traversal issues, so my conclusion
from that understanding is that the draft is more likely to get community
review in BEHAVE than outside BEHAVE, and the topic is closer to BEHAVE's
scope than any other obvious working group.
Thanks,
Spencer
