RE: [Enum] How to correctly set up the request URI?

["Stastny Richard" <Richard.Stastny at oefeg.at>]

Thank you, Tom

just a minor additional question:

> In either case, after the provider A proxy performs an ENUM query and
> rewrites the request URI, it should behave as a UAC and follow the
> procedures outlined in Section 4 of RFC3263 to determine the IP
address,
> port, and transport protocol for the provider B UAS.

If I have to do this according to RFC3263 anyway, why put
the sbc4711.provB.net into ENUM in the first place?

-sta


> -----Original Message-----
> From: Creighton, Tom [mailto:Tom_Creighton at cable.comcast.com]
> Sent: Thursday, June 01, 2006 4:36 PM
> To: Stastny Richard; speermint at ietf.org
> Cc: enum at ietf.org
> Subject: RE: [Enum] How to correctly set up the request URI?
> 
> 
> 
> > -----Original Message-----
> > From: Stastny Richard [mailto:Richard.Stastny at oefeg.at]
> > Sent: Thursday, June 01, 2006 09:06
> > To: speermint at ietf.org
> > Cc: enum at ietf.org
> > Subject: [Enum] How to correctly set up the request URI?
> >
> > Folks,
> >
> > Question for clarification:
> >
> > In the discussions here on how to populate sip URI in Infrastructure
> > ENUM to derive the Call Routing data for SPEERMINT  two
> > lines of thought exist:
> >
> > The Enumservice SIP in Infrastructure ENUM should contain
> > 1. the address-of-record of the user: e.g. sip:+4319793321 at provB.net
> > 2. the ingress point into the provider network:
> > e.g. sip:+4319793321 at sbc4711.provB.net
> >
> > The originating UAC has in this case set the To: field to
> > tel:+4319793321 and the Request-URI to e.g.
> > sip:+4319793321provA.net;user=phone. This caused the
> > ENUM query at the proxy of provider A
> >
> > The question is how the proxy of provider A is now
> > setting up the request URI in cases mentioned above?
> >
> > Does the UAS from provider B accept calls to sbc7411.provB.net,
> > or must the request URI set to the proper AoR as described in
> > 8.2.2.1 of RFC 3261? If yes, only option 1 is possible in ENUM.
> 
> [Tom Creighton wrote:]
> From section 8.2.2.1 of RFC3261:	"If the Request-URI does not
> identify an address that the UAS is willing to accept requests for, it
> SHOULD reject the request with a 404 (Not Found) response."
> 
> As long as the UAS from provider B is "willing" to accept the request,
> either should work.  Since provider B is populating Infrastructure
ENUM,
> one would hope that they would coordinate this data with the
> configuration of their proxies.
> 
> Besides, how do you actually know that sbc4441.provB.net is actually a
> hostname and isn't a subdomain?
> 
> In either case, after the provider A proxy performs an ENUM query and
> rewrites the request URI, it should behave as a UAC and follow the
> procedures outlined in Section 4 of RFC3263 to determine the IP
address,
> port, and transport protocol for the provider B UAS.
> 
> >
> > I would also like to draw the attention to section 3 of
> > RFC3761 (SIP Enumservice) explaining the usage of AoR in
> > ENUM.
> >
> > Regards
> >
> > -sta
> >
> >
> > _______________________________________________
> > enum mailing list
> > enum at ietf.org
> > https://www1.ietf.org/mailman/listinfo/enum

_______________________________________________
enum mailing list
enum at ietf.org
https://www1.ietf.org/mailman/listinfo/enum