Re: New I-D:draft-kaplan-enum-source-uri-00.txt
Paul Erkkila <[email protected]>
| Newsgroups | gmane.ietf.enum |
|---|---|
| Message-ID | <[email protected]> |
I think this is interesting work in the process of rolling more SCP functionality using ENUM as a building block.Implementations would certainly ease the transition off of current routing methods and move us closer to a "unified dip" model for routing. I definitely support it. The first issue I can think of is that it _seems_ primarily targeted towards the carrier ENUM/private peering space and might not see much use in the open spaces. The second issue is that I think some discussions with DNS folk about securing the query information (and validation). At note should at least be made of the possibility of using enumeration of the URI space to gain access to different response data. (similar to domain/space walking). -pee Hadriel Kaplan wrote: > Howdy, > > We just submitted an I-D for a mechanism to include the source URI > information in ENUM queries, primarily targeted at including the > From/PAI SIP/Tel URI of the SIP Request which triggered the ENUM lookup, > so the ENUM server can provide a response based on that. This is useful > for performing source-based ENUM routing and filtering. > > > > The I-D is available at: > > http://www.ietf.org/internet-drafts/draft-kaplan-enum-source-uri-00.txt > > > > We plan on presenting this in Philadelphia, but given the winding down > of the ENUM WG we'd like to get comments now and see if there is > interest in progressing this. > > Thanks! > > > > -hadriel > > > > !DSPAM:475f12da304357515877532! > > > ------------------------------------------------------------------------ > > _______________________________________________ > enum mailing list > [email protected] > https://www1.ietf.org/mailman/listinfo/enum > > > !DSPAM:475f12da304357515877532!