Current draft (with Recv fix):

Info-Package        =  "Info-Package" HCOLON Info-package-type
  Send-Info           =  "Send-Info" HCOLON Info-package-type
                         *( COMMA Info-package-type )
  Recv-Info           =  "Recv-Info" HCOLON Info-package-type
                         *( COMMA Info-package-type )
  Info-package-type   =  Info-package-name *( "." Info-package-param)
  Info-package-name   =  token-nodot
  token-nodot         =  1*( alphanum / "-"  / "!" / "%" / "*"
                             / "_" / "+" / "`" / "'" / "~" ) ;rfc3265
  Info-package-param  =  generic-param  ;this doesn't work due to dot!


From an implementation perspective, this is unnecessarily complex and verbose: if a UA can both send and receive the same INFO package, it must list it twice.

As an alternative, I would propose something similar to SDP media streams:

Supported-Info      = "Supported-Info" HCOLON Info-package-type *(COMMA 
Info-package-type)
Info-package-type   = token *( SEMI Info-package-param )
Info-package-param  = "sendonly" / "recvonly" / generic-param ; only one of "sendonly" or 
"recvonly" may be present

Usage would be to include 1 "Supported-Info" header in requests/responses, instead of 2 separate "Send-Info" / "Recv-Info". By default a package is "sendrecv" (i.e. UA may send it, and can receive it), unless overridden by "sendonly" or "recvonly" flags

Regards,
Jeroen


_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip

Reply via email to