Re: [rtcweb] NAT Draft

[Magnus Westerlund <[e-mail]>]

On 2011-11-05 00:35, Hadriel Kaplan wrote:
> 
> 
> On Nov 4, 2011, at 5:20 AM, Magnus Westerlund wrote:
> 
>> 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?
> 
> Hey you're one of the Chairs - if the Chairs want to have a dozen
> RFCs on requirements, and another dozen on actual behavior, that's
> your call. Seems silly to me, but most of the admin work is on the
> authors, the Chairs, and the ADs I think... so it's no skin off my
> nose to have more RFCs.

No, you misunderstood me, or more likely I wasn't clear enough. I at
least, expect the NAT draft to define how to actually do it. Not
requirements on the solution.


> 
> As I said in my email: draft-ietf-rtcweb-use-cases-and-requirements
> is high-layer/general WebRTC requirements, and if we want a separate
> detailed specification, that would make sense (or even multiple if
> that's your preference).  But draft-cbran-rtcweb-nat-02 doesn't
> appear to be that - it reads like a requirements for NAT traversal
> mechanism, and that the answer to that is native ICE support.

Agreed, and I do expect the document to go in the direction of a
specification of what is needed to implement by the WebRTC end-point.

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]
----------------------------------------------------------------------