BoF Request, IETF 71, Philadelphia, Pennsylvania, USA
BoF:  SIP-E164, SIP E164
Requester:  Dan Wing, dwing@cisco.com
Chairs:  TBD


   SIP has long supported the use of both email-style addresses
   (user@host) and telephone-style addresses (number@host) in the
   "From:" address.  A significant number of SIP deployments use the
   latter style with E.164 numbers.  

   A SIP URI containing an E.164 number received in a From header field
   is not a reliable source domain of a request, even when authenticated
   by means of the Identity header field.  Only the E.164 number itself
   can be considered reliable, and only the E.164 itself is suitable for
   comparing with known identities at the destination (e.g., in a white
   list, in an address book).The inability to depend on the domain part
   of an E.164 SIP URI is a serious deficiency in some situations.

   This BoF is intended to discuss this problem.


BoF Goals:

  1. Determine if work should be chartered to allow a SIP element to
     determine which domain(s) own(s) an E.164 number.



Agenda:

  title                                                   duration
  ---------------------------                          -----------
  Introduction                                          (chairs, 5)

  SIP E.164 Problem Statement                          (Elwell, 30)
    draft-elwell-sip-e164-problem-statement (not published)

  Discussion                                       (all, remaining)
                                                       ------------
                                                       total:  120