Re: [rtcweb] NAT Draft

[Magnus Westerlund <[e-mail]>]

On 2011-11-04 02:59, Hadriel Kaplan wrote:
> 
> Howdy,
> I've read the draft and I do think some consensus has been reached with
> regard to some of it.
> 
> Having said that, though, I don't think this needs to be a WG document
> because that implies we would be publishing this as an RFC eventually...
> and I don't see a need to do that.
> 
> We should instead incorporate any requirements we reach WG consensus on
> into the draft-ietf-rtcweb-use-cases-and-requirements WG document; or if
> we feel that that document is meant for high-level requirements only,
> then we should create a new WG document that covers all the specific
> requirements.  
> 
> Having separate individual drafts is ok for now, but having a separate
> WG doc and RFC for every requirement sub-category seems unnecessary to
> me, and likely to cause confusion.  It's not like we would expect to
> only satisfy the requirements of RFC X but not Y, is it?  

Hadriel,

I think a document of this type should and will eventually be published
as its own RFC. The reason for this I think is that the document should
evolve from requirements to actually specify how the Peer to Peer
transport flow establishment layer for WebRTC works. As that layer will
be used by both the RTP based media transport and the Data Transport
having a document only containing that functionality will make it
simpler to reference.

In addition I think it is good from specification maintenance
perspective. If we have bugs in a functionality block we don't need to
republish other functionality blocks just to update, in this case the
NAT traversal functionality.

Given that a NAT traversal document will specify how WebRTC establish
the transport flows do you think that really should be part of the
use-cases and requirements?

My personal input to draft-cbran-rtcweb-nat is to stop using
requirements as the word for what an end-point shall implement and which
specifications they should follow. Instead call it specification.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  [phone]
Färögatan 6                | Mobile [phone]
SE-164 80 Stockholm, Sweden| mailto: [e-mail]
----------------------------------------------------------------------