"Dale R. Worley" <[EMAIL PROTECTED]> asks:
> I'm looking into the definition of NAPTR records. All I can find is the
> fearsomely general RFC 2915, and the very specific RFC 3263. How is the
> "service field" defined (that is "SIP+D2U" and friends)? Is there a
> registry for all the possible values of this field? Are there accepted
> principles for how these values are constructed?
RFC 3403 and friends (3401 - 3405) obsolete RFC 2915.
RFC 3404, section 4.4:
4.4 Services Parameters
Service Parameters for this Application take the form of a string of
characters that follow this ABNF:
service_field = [ [protocol] *("+" rs)]
protocol = ALPHA *31ALPHANUM
rs = ALPHA *31ALPHANUM
; The protocol and rs fields are limited to 32
; characters and must start with an alphabetic.
In other words, an optional protocol specification followed by 0 or
more resolution services. Each resolution service is indicated by an
initial '+' character.
The empty string is also valid. This will typically be seen at the
beginning of a series of Rules, when it is impossible to know what
services and protocols will be offered at the end of a particular
delegation path.
Hope that helps,
frank
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
