[BEHAVE] Prefix length enumeration

To: Behave WG <behave at ietf.org>, draft-ietf-behave-address-format at tools.ietf.org
Subject: [BEHAVE] Prefix length enumeration
From: Simon Perreault <simon.perreault at viagenie.ca>
Date: Sun, 08 Nov 2009 07:46:40 +0900
Delivered-to: behave at core3.amsl.com
List-archive: <http://www.ietf.org/mail-archive/web/behave>
List-help: <mailto:behave-request@ietf.org?subject=help>
List-id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-post: <mailto:behave@ietf.org>
List-subscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
List-unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
User-agent: Thunderbird 2.0.0.23 (Macintosh/20090812)

Hello,

draft-ietf-behave-address-format presents an enumeration of 6 IPv6
prefix lengths that can be used as Pref64::/n.

As an implementor, I was wondering if they were just examples and
whether other lengths were allowed. This would have a big impact in the
code.

I would like to see a clear indication that other prefix lengths are
disallowed. This lets me safely optimize for the 6 lengths listed.

Thanks,
Simon
-- 
DNS64 open-source   --> http://ecdysis.viagenie.ca
STUN/TURN server    --> http://numb.viagenie.ca
vCard 4.0           --> http://www.vcarddav.org

Follow-Ups:
- Re: [BEHAVE] Prefix length enumeration
  - From: Xing Li

Prev by Date: Re: [BEHAVE] [NAT64] Hairpinning loop
Next by Date: Re: [BEHAVE] [NAT64] Hairpinning loop
Previous by thread: [BEHAVE] Review of draft-boucadair-behave-dns-a64-01
Next by thread: Re: [BEHAVE] Prefix length enumeration
Index(es):
- Date
- Thread

[BEHAVE] Prefix length enumeration

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.