[martini] #60: Optionality of Service-Route etc.

["martini issue tracker" <[e-mail]>]

#60: Optionality of Service-Route etc.
------------------------------------------------+---------------------------
 Reporter:  john.elwell@…                       |       Owner:     
     Type:  defect                              |      Status:  new
 Priority:  minor                               |   Milestone:     
Component:  gin                                 |     Version:     
 Severity:  In WG Last Call                     |    Keywords:     
------------------------------------------------+---------------------------
 In section 7:
 "The following sections describe the means by which this mechanism
    interacts with relevant REGISTER-related extensions currently defined
    by the IETF."

 Perhaps there should be clarification as to whether or not this document
 requires support of any of these mechanisms. For example, I don't think
 there is any intention to mandate support of the Service-Route header
 field - section 7.4 just gives information on the impact if the mechanism
 is used. Similarly Path is optional, beyond the specific bits mandated
 elsewhere. I don't think there is any intention to mandate support for the
 registration event package (7.2) or SIP-Outbound (7.3). Concerning support
 for public and temporary GRUUs (7.1), I think this is the subject of a
 separate discussion. Depending on what is decided for each of these,
 either a blanket statement in 7 or individual statements in 7.1/2/3/4
 should be added.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/60>
martini <http://tools.ietf.org/martini/>