looking at rfc 3455:
ftp://ftp.rfc-editor.org/in-notes/rfc3455.txt
P-Access-Network-Info = "P-Access-Network-Info" HCOLON
access-net-spec
access-net-spec = access-type *(SEMI access-info)
access-type = "IEEE-802.11a" / "IEEE-802.11b" /
"3GPP-GERAN" / "3GPP-UTRAN-FDD" /
"3GPP-UTRAN-TDD" /
"3GPP-CDMA2000" / token
access-info = cgi-3gpp / utran-cell-id-3gpp /
extension-access-info
extension-access-info = gen-value
cgi-3gpp = "cgi-3gpp" EQUAL
(token / quoted-string)
utran-cell-id-3gpp = "utran-cell-id-3gpp" EQUAL
(token / quoted-string)
Regarding access-info, it's very unusual that an extension
parameter grammar isn't grammatically compatible with the
non-extension parameters.
Why is the extension-access-info only a gen-value
when the other access-info's can have EQUAL?
Wouldn't generic-param be more reasonable?
extension-access-info = generic-param
( from RFC3261
generic-param = token [ EQUAL gen-value ]
gen-value = token / host / quoted-string )
Then I could have
P-Access-Network-Info:
X-MY-PROPRIETARY-NET;x-network-id=12;x-node-id=23
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
