I agree as well. Informational is a good choice. 

BCP would be quite far fetched.  

>-----Original Message-----
>From: [email protected] [mailto:[email protected]] On 
>Behalf Of ext Elwell, John
>Sent: 07 January, 2009 13:12
>To: Shida Schubert; [email protected]
>Cc: Drage, Keith (Keith)
>Subject: Re: [Sip] BCP or Informational: Mechanisms for UA 
>initiated privacy
>
>I agree.
>
>John 
>
>> -----Original Message-----
>> From: Shida Schubert [mailto:[email protected]]
>> Sent: 07 January 2009 10:43
>> To: [email protected] List
>> Cc: Elwell, John; Drage, Keith (Keith)
>> Subject: BCP or Informational: Mechanisms for UA initiated privacy
>> 
>> 
>>   At the last meeting, Keith asked the group to provide feedback on 
>> whether the draft-ietf-sip-ua-privacy addressing the milestone 
>> "Mechanisms for UA initiated privacy" should proceed as BCP or as an 
>> informational.
>> 
>>   As a co-author of the draft, my inclination is to go informational.
>> 
>>   Reason is because the 2 specifications the draft requires, namely 
>> GRUU and TURN aren't widely deployed, and neither are RFCs (Although 
>> GRUU I believe is pretty close.).
>> 
>>   Despite the fact that people I talked to are keen on implementing 
>> these specifications, I don't think the draft which requires and 
>> depends on specifications that aren't widely deployed neither RFC 
>> should be proceeded as a Best Current Practice..
>> 
>>   Regards
>>    Shida
>> 
>>   
>> 
>_______________________________________________
>Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>This list is for NEW development of the core SIP Protocol Use 
>[email protected] for questions on current sip 
>Use [email protected] for new developments on the application of sip
>
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [email protected] for questions on current sip
Use [email protected] for new developments on the application of sip

Reply via email to