Dean  Willis stated the NOTE WELL

Agenda Bash  for Session  2

SIPS-Guidelines: Francois


Intended status of the draft:   

Make this an RFC 4485 compliant Standards track document?        
 No Consensus 



Deprecation of the ÒLast Hop ExceptionÓ?               
Agreed to deprecate

The deprecate decision makes what ever document the deprecate goes in as standards 
track and an update to RFC 3261 and part of the ÒEssential CorrectionsÓ RFC.


Do we charter providing a solution to the true End to End security problem? 
No Consensus. Anything needs to be well described and describe the threat model


Outbound: Cullen

TCP keepalives 
Option 1: DonÕt Do CRLF
Option 2: Keep text in 08 version
	
Rough Consensus to go with Option 2


When does the client have to do Keep alives?
YES to proposal in CullenÕs slides


One Instance ID (UUID)É..
No Consensus so Outbound will allow use of other URNs

One Algorithm for flow tokens      
Consensus One Algorithm

Configuration of the URI that indicates STUN 

Advice about OPTION probing for STUN     
Consensus is to Delete the Should sends an option for probing text and the May send

120 Failure timer issue    delete this text


SIP URI discover using DNS-SD: Henning

Determining Request Destination     Define the problem, and discuss with DNS crowd


Clarification of Privacy: Mayumi

Questions:
Is the direction of the draft correct?       

Should privacy function be executed solely on the UA?      

Obsolete or update RFC 3323 and redefine Privacy header with new priv-values?      

Separate into two drafts (one updating RFC 3323 and one defining endpoint oriented privacy)?     

Consensus is to carry this work forward and worked into the charter


Addressing record-Route-Issues: Thomas

Proposed standard or BCP
No Consensus but interest in doing this work.