Brett, The answer for your question is “both”, at least that was the intention. Thanks, Tolga From: Haluska, John J [mailto:jhaluska@xxxxxxxxxxxxx] Dan, I’ll take a look and let you know – I’m out of MIPS at the moment. Thanks for continuing with this even though you’ve moved on. John From: Dan York [mailto:dan-ietf@xxxxxxxxxxx] Brett, (and replying from a slightly different address so that it will go to the SIPPING list) Thank you for the feedback and question. The ABNF in the draft has evolved over the past almost-4 years as various people more literate than I in ABNF have given us feedback and we've updated the draft. In the ABNF section, "chargeparam" is intended to represent that you could optionally have the "noa", "npi" parameters - or any other generic parameters found in RFC 3261(such as "user=phone") Originally, the ABNF read: P-Charge-Info = "P-Charge-Info" HCOLON (name-addr / addr-spec)* (SEMI charge-param) ; name-addr and addr-spec are specified in RFC 3261 charge-param = npi-param / noa-param / generic-paramI thought that was fairly clear and made sense. However, I changed the ABNF in rev -10 in October 2010 to more simply: P-Charge-Info = "P-Charge-Info" HCOLON (name-addr / addr-spec) ; name-addr and addr-spec are specified in RFC 3261 charge-param = npi-param / noa-param / generic-paramafter someone strongly made the case that the "* (SEMI charge-param)" was not required because it was a "userinfo parameter" to the name-addr/addr-spec element. Unfortunately, the email exchange about this seems to have NOT taken place on the mailing list but rather in a private email exchange - and I no longer have access to the archives of the email account where that occurred (I am no longer with Voxeo) - so I don't know who it was that argued for this change. I'm directly cc'ing John Haluska as he was involved in with a number of those exchanges and can perhaps clarify this. In reviewing section 19.1.1 of RFC 3261 ( http://tools.ietf.org/html/rfc3261#section-19.1.1 ) and sections 19.1.2, 19.1.3, and 19.1.6 as well as the ABNF in section 25, I am guessing that the rationale was because the "charge-param" does fit into the "user" section of the URI. So that's a roundabout way of saying that it is part of "user", as I interpret the ABNF in RFC 3261. Do you have suggestions for how to make this clearer in the draft? Would the original ABNF be more useful to you? Should the sentence "charge-param is used as a userinfo parameter in P-Charge-Info" indicate that it is the "user" part of the "userinfo" field? Thanks, Dan P.S. After not receiving any feedback for many, many months I suddenly have received two email questions/comments about P-Charge-Info today. I don't know if this is as a result of the mention on a mailing list that Richard Shockey mentioned... but I was surprised. On Nov 29, 2011, at 1:35 PM, Brett Tate wrote: Howdy, -- Phone: +1-802-735-1624 skype:danyork -- -------------------------------------------------------- All comments and opinions are entirely my own and have no connection whatsoever to any employer, past or present. Indeed, by tomorrow even I might be disavowing these comments. -------------------------------------------------------- |
_______________________________________________ Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping This list is for NEW development of the application of SIP Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip Use sip@xxxxxxxx for new developments of core SIP
