[Sip] Query: Adopt draft-willis-sip-path-xx as WG doc?

["Dean Willis" <dean.willis@softarmor.com>]

The document draft-willis-sip-path-01.txt introduces the Path extension header suggested by 3GPP in the Garcia 3GPP requirements draft in SIPPING.

 

The basic requirements being met are to 1) allow a UA to REGISTER a contact which requires traversing a sequence of proxies on future messages between the registrar and the UA, with that sequence dynamically discovered during the REGISTER, and 2) allow a UA to discover from a REGISTER response a sequence of proxies between it and a known proxy offering outbound services for that UA.

 

 

The approach taken in the draft generalizes the 3GPP requirements by allowing the sequences to be asymetric-- for example, the inbound and outbound sequences might traverse different proxies, or there might only be a sequence in one direction (A firewall proxy sits between UA and its registrar, but UA does not use the registrar for outbound services).

 

I'd like to poll for three things:

 

1) Do we want to address the requirements raised by 3GPP?

 

2) Do we have a general consensus on something like the PATH header as an appopriate mechanism?

 

3) Is draft-willis-sip-path-01.txt a reasonable baseline document?

 

If we have consensus on all three accounts, I propose to accept draft-willis-sip-path-01.txt as a working group document, and pursue future revisions as draft-ietf-sip.xx.

 

If not, then please make a counterproposal.

 

Opinions, please.

 

--

Dean