[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: IANA assignment policies

To: ipsec@xxxxxxxxxxxxxxxxx
Subject: Re: IANA assignment policies
From: Paul Hoffman / VPNC <paul.hoffman@xxxxxxxx>
Date: Wed, 18 Feb 2004 13:49:53 -0800
In-reply-to: <>
References: <16434.22666.257287.681344@fireball.acr.fi> <15123.1077047999@marajade.sandelman.ottawa.on.ca> <>
Sender: owner-ipsec@xxxxxxxxxxxxxxxxx

"Reserved for IANA" is a silly and confusing convention that early IPsec documents used. Everything is reserved for IANA that is not allocated, yes? Having "reserved" meaning "IANA should never allocate" and "reserved for IANA" meaning "IANA should allocate" is bound to end up in tears. Drop all the "reserved for IANA" strings. Any developer who really cares can figure out what the last available number in a range is.

--Paul Hoffman, Director
--VPN Consortium

References:
- Re: IANA assignment policies
  - From: Tero Kivinen

Prev by Date: SAs that carry fragments Was: Re: Some IKEv2 issues
Next by Date: Re: SAs that carry fragments Was: Re: Some IKEv2 issues
Previous by thread: Re: IANA assignment policies
Next by thread: Changing the key deriveration
Index(es):
- Date
- Thread