1. SIP and ENUM
Old draft-ietf-sipping-e has been split into child drafts
Now there is draft-peterson-enum-sip-00, a smaller text which only defines the enumservice itself
SIPPING document will continue, with guidelines for SIP users
That document has some new considerations (rfc2916bis)
Approach of this draft considers only SIP addresses-of-record
Not ‘contact addresses’ that represent devices
Defines only an ‘E2U+SIP’ enumservice
This follows the syntax we agreed to in Yokohama – will that be reflected in rfc2916bis?
No further granularity required for addresses-of-record
No known open issues (anyone else got any?)
WG item?

2. ENUM & SIP ENUM query returns AoR, LS query returns contact VoIP.biz
LS query:
LS response:
Location Service
VoIP.biz
PC113
(Location of Joe)
INVITE
INVITE
ENUM query:
ENUM response:
ENUM server
ENUM query returns
AoR, LS query
returns contact
Number: