Re: Regarding RFC 5404

Ravi,

Not sure if you have raised in RFC errata, but it is already seen based on your query.

http://www.rfc-editor.org/errata_search.php?rfc=5404&rec_status=15&presentation=table

Thanks,
Manju

-----Original Message-----
From: sip-implementors-bounces <at> lists.cs.columbia.edu
[mailto:sip-implementors-bounces <at> lists.cs.columbia.edu] On Behalf Of Ravi Kumar
Sent: Saturday, 02 June, 2012 7:27 PM
To: sip-implementors <at> lists.cs.columbia.edu
Subject: [Sip-implementors] Regarding RFC 5404

Hi All,

RFC 5404 section 
7.1.  Media Type Definition

int-delay:  

         int-delay = "int-delay:" source-delay *("," source-delay)

         source-delay = SSRC ":" delay-value

         SSRC = 1*8HEXDIG ; The 32-bit SSRC encoded in hex format

         delay-value = 1*5DIGIT ; The delay value in milliseconds

         Example: int-delay=ABCD1234:1000,4321DCB:640

         NOTE: No white space allowed in the parameter before the end of
         all the value pairs

7.2.  Mapping to SDP

   o  Any remaining parameters go in the SDP "a=fmtp" attribute by
      copying them directly from the media type parameter string as a
      semicolon-separated list of parameter=value pairs.

As per section int-delay parameter should be part of a=fmtp line and it
should have parameter as parameter=value pair.

But as per ABNF it should be int-delay:<value>

Also example mentions that int-delay=<value>

This looks like bug in RFC. Please confirm which is correct ABNF.

Regards,

Ravi Kumar

_______________________________________________
Sip-implementors mailing list
Sip-implementors <at> lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors