Hi Carsten, RFC 2915 and 2916 are now obsolete. Please check the latest ones. An overview of the relevant ENUM specs are listed here:
http://www.ag-projects.com/content/view/61/96/ Regards, Adrian On Apr 7, 2008, at 11:12 AM, Carsten Bock wrote: > Hi everybody, > > i have a question regarding the implementation of ENUM in OpenSER and > the NAPTR RFC (RFC2915): > >> From the doc's of the ENUM Module of OpenSER 1.3: > "Then enum_query sorts the chosen NAPTR records based on their <order, > preference>. After sorting, enum_query replaces the current Request > URI > by applying regexp of the most preferred NAPTR record its user part > and > appends to the request new branches by applying regexp of each > remaining > NAPTR record to the user part of the current Request URI." > > Is this behaviour compliant with RFC2915, Chapter 11 [Notes]? > > Quote: > "11. Notes > > o A client MUST process multiple NAPTR records in the order > specified by the "order" field, it MUST NOT simply use the first > record that provides a known protocol and service combination." > http://tools.ietf.org/html/rfc2915#section-11 > > Is it correct, that in the case of different priorities parallel > forking > is used? Shouldn't it be sequential forking? > > Thank you, > > Carsten > > > _______________________________________________ > Devel mailing list > Devel@lists.openser.org > http://lists.openser.org/cgi-bin/mailman/listinfo/devel _______________________________________________ Devel mailing list Devel@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/devel
