Hi, Draft-kaplan-dispatch-info-dtmf-package-00's ABNF conflicts with the example. Based upon 2008 email discussion with Hadriel (when it was draft-kaplan-sipping-dtmf-package-00), my understanding is that the ABNF would be fixed (instead of the example) to include CRLF after duration.
"D'oh! Ya well, the example is the normative part. :) (will fix it for the update... if info ever gets on the docket)" > -----Original Message----- > From: brez [mailto:brez...@gmail.com] > Sent: Thursday, December 19, 2013 9:17 AM > To: iancu laura; sip-implementors@lists.cs.columbia.edu > Subject: Re: [Sip-implementors] sip info message body CRLF > > On 12/19/2013 12:47 PM, iancu laura wrote: > > So, you are saying that the syntax should be as follows,for example: > > > > Content-type: application/dtmf-relay<CR><LF> > > Content-length:26<CR><LF> > > <CR><LF> > > Signal=2<CR><LF> > > Duration=250<CR><LF> > > > > Is <cr><lf> absolutely mandatory after Duration=250?? > > And if it really is, in which RFC is this mentioned? > > Syntax defined in Section 5.2. INFO Bodies, of > draft-kaplan-dispatch-info-dtmf-package-00, does not require CRLF after > the duration. > > But there is a thing to be noted regarding the particular example you > give above. The Content-Length is 26, but in the message body you have > only 24 characters - you miss 2 characters as there are no SP between > "=" and the values. Your example is similar to that in Section 6. > Example Exchange, where total body length is 26 with <CRLF>'s and SP > between "=" characters: > > Content-Type: application/dtmf-relay<CR/LF> > Content-Length: 26<CR/LF> > <CR/LF> > <CR/LF> > Signal= 6<CR/LF> > Duration= 100<CR/LF> > > > Regards, > > Brez > > > _______________________________________________ > Sip-implementors mailing list > Sip-implementors@lists.cs.columbia.edu > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
