Hello Interpreting "token1=token2" as 'm-paramter' or 'accept-parameter' depends on the m-type and sub-type fields. For your case I guess that they be considered as 'accept-paramter' as no media is specified.
True implmentation of Accept grammer causes ambiguity as grammer does not differentiate between 'm-parameter' and 'accept-param' tokens. The most appropriate interpretation will be context dependent as mentioned above. Regards, Salman Abdul Baset Design Engineer Avaz Networks -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Satyanarayana T Sent: Tuesday, July 09, 2002 12:01 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: [Sip-implementors] Issue with Accept grammar? Hi all, In the header, Accept: */*;token1=token2;q=0.9 Should "token1=token2" be taken as accept-param or m-parameter? Grammar is reproduced here for your convenience: Accept = "Accept" HCOLON [ accept-range *(COMMA accept-range) ] accept-range = media-range *(SEMI accept-param) media-range = ( "*/*" / ( m-type SLASH "*" ) / ( m-type SLASH m-subtype ) ) *( SEMI m-parameter ) accept-param = ("q" EQUAL qvalue) / generic-param qvalue = ( "0" [ "." 0*3DIGIT ] ) / ( "1" [ "." 0*3("0") ] ) generic-param = token [ EQUAL gen-value ] gen-value = token / host / quoted-string m-parameter = m-attribute EQUAL m-value m-attribute = token m-value = token / quoted-string regards Satya T -----Original Message----- From: The IESG [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 09, 2002 3:15 AM Cc: [EMAIL PROTECTED] Subject: [Sipping] Last Call: ISUP to SIP Mapping to Proposed Standard The IESG has received a request from the Session Initiation Proposal Investigation Working Group to consider publishing each of the following internet drafts as as Proposed Standards. o 'ISUP to SIP Mapping' <draft-ietf-sipping-isup-03.txt> o Mapping of ISUP Overlap Signalling to the Session Initiation Protocol <draft-ietf-sipping-overlap-01.txt> The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the [EMAIL PROTECTED] or [EMAIL PROTECTED] mailing lists by August 05, 2002. Files can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-sipping-isup-03.txt http://www.ietf.org/internet-drafts/draft-ietf-sipping-overlap-01.txt _______________________________________________ Sipping mailing list https://www1.ietf.org/mailman/listinfo/sipping This list is for NEW development of the application of SIP Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments of core SIP _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
