Hi Iñaki,

I think 3261 explains the nomenclature

7.3.1 Header Field Format

   The format of a header field-value is defined per header-name.  It
   will always be either an opaque sequence of TEXT-UTF8 octets, or a
   combination of whitespace, tokens, separators, and quoted strings.
   Many existing header fields will adhere to the general form of a
   value followed by a semi-colon separated sequence of parameter-name,
   parameter-value pairs:

         field-name: field-value *(;parameter-name=parameter-value)

The format you indicated is general form as explained in the last 
sentence but is not a universal SIP ABNF rule for header-value.  Thus 
the second sentence generally applies to the header-value format or:

header-value = 1*(  
<http://www.tech-invite.com/Ti-sip-abnf.html#alphanum>alphanum  /   "-" 
  /   "."   /   "!"   /   "%"   /   "*"  /   "_"   /   "+"   /   "`"   / 
  "'"   /   "~" )

Joegen

Iñaki Baz Castillo wrote:
> Hi, a SIP header si divided into:
>
>   header  =  "header-name" HCOLON header-value *(COMMA header-value)
>
> And each header-value is divided into:
>
>   header-value = CORE-VALUE *(;parameter-name=parameter-value)
>
> My question is: how to name this "CORE-VALUE" correctly?
>
> For example, in this header:
>
>   From: "Pepe" <sip:[EMAIL PROTECTED]>;phone;online=yes
>   - header-name = From
>   - header-value = "Pepe" <sip:[EMAIL PROTECTED]>;phone;online=yes
>   - CORE-VALUE = "Pepe" <sip:[EMAIL PROTECTED]>"
>   - *(;parameter-name=parameter-value) = ;phone;online=yes
>
> I've found in RFC3261 but cannot find the appropiate nomenclature. Thanks for 
> any help.
>
>
>   
> ------------------------------------------------------------------------
>
> No virus found in this incoming message.
> Checked by AVG. 
> Version: 7.5.518 / Virus Database: 269.21.7/1325 - Release Date: 3/11/2008 
> 1:41 PM
>   



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

Reply via email to