Re: [hybi] header definitions in -13

Iñaki Baz Castillo <ibc@aliax.net> Fri, 02 September 2011 12:03 UTC

MIME-Version: 1.0
In-Reply-To: <4E60C588.2060703@isode.com>
References: <4E5E983A.2000004@gmx.de> <4E60C588.2060703@isode.com>
Date: Fri, 02 Sep 2011 14:04:42 +0200
Message-ID: <CALiegfn_eQ1x+Dt9VAhYp1zMOZPagUtd+9yAN7Qvp_Do6HioJA@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] header definitions in -13
Precedence: list

2011/9/2 Alexey Melnikov <alexey.melnikov@isode.com>:
> I think definitions in the IANA registration section are what you are asking
> for. Maybe they are missing some cross-references.
>
> If that is not what you are asking for, then please provide an example of
> how such a definition might look like for a single header field.

IMHO IANA section is not the good place to widely describe all the
implied new headers in this specification. IANA section is like a
"mandatory" section to make happy some people/organizations. IMHO the
document itself (out of the IANA section) should have a specific
section describing (not in depth) each header.

For example, RFC 3261 (SIP) has a section describing each header field:
  http://tools.ietf.org/html/rfc3261#section-20

and also there is an IANA section for that:
  http://tools.ietf.org/html/rfc3261#section-27.3

-- 
Iñaki Baz Castillo
<ibc@aliax.net>

[hybi] header definitions in -13 Julian Reschke
Re: [hybi] header definitions in -13 Iñaki Baz Castillo
Re: [hybi] header definitions in -13 Alexey Melnikov
Re: [hybi] header definitions in -13 Iñaki Baz Castillo