Re: [PEPPERMINT] DRINKS PROPOSED Charter ..comments please.

> -----Original Message-----
> From: Otmar Lendl [mailto:lendl@labs.nic.at] On Behalf Of Otmar Lendl
> Sent: Wednesday, April 23, 2008 11:41 AM
>
> On 2008/04/23 16:04, Richard Shockey <richard@shockey.us> wrote:
> > >
> > >     More specifically, the SED is the set of parameters that the local
> > >     SSP needs to complete the call, through its egress SBE's, and may
> > >     include:
> >
> > Number ranges?
>
> As it is defined, SED is what you get from the mapping step, not the
> mapping itself.
>
> Number ranges (or individual numbers) are the key under which SED is
> stored.
>
> (In the case where ENUM is the access protocol, SED would be whatever is
> contained in the NAPTR. The number ranges don't appear there, they are
> only relevant for selecting the right NAPTR records from the DNS tree.)

Yes exactly - afaik, the SED is the result of the lookup, vs. the keys for the lookup; but a couple people actually sent me email asking why number ranges weren't in the list, so maybe that's not a common definition. (and the keys do overlap with the results)  In reading the terminology draft it sure sounds like SED is returned by the LRF, not used for LUF/LRF lookups.

I think though what you're looking for is a minimal list of the data which needs to be exchanged between providers or between provider-regstry? (ie, the both lookup keys and results)
Then I think a starting list would be like:

     . Destination matching criteria, possibly of one or more of the
       following:

          o  An E.164 number, number range, or prefix

          o  A domain name or FQDN

     . One or more originating qualifiers, possibly including one or more
       of the following

          o  A source SIP/SIPS/TEL URI match filter

          o  A source domain identified as an SSP-ID

          o  Source geographic or topological identifiers

     . A SIP next-hop/next-hop-group to send the request to, possibly
       including one or more of the following:

          o  Fully Qualified Domain Name (FQDN)

          o  Learned/static SIP Route headers for the peer SSP

     . A resolved terminating domain identifier, which may include:

          o  The terminating domain identified as a Domain Name

          o  The terminating domain identified as an SSP-ID

          o  One or more parameters indicating ported number resolution

     . Optional resource control parameters such as

          o  Resource priority value(s) for the call

          o  Geographic or topological identifiers

Note there are plenty of other matching criteria used today, such as time of day, originating and destination trunk groups, method type, session type, media type, codec types, etc.  But I'm hoping we can avoid those for now.

-hadriel
_______________________________________________
PEPPERMINT mailing list
PEPPERMINT@ietf.org
https://www.ietf.org/mailman/listinfo/peppermint