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

Re: Remaining open issues for RFC-2401bis

To: Karen Seo <kseo@bbn.com>
Subject: Re: Remaining open issues for RFC-2401bis
From: Bill Sommerfeld <sommerfeld@east.sun.com>
Date: Fri, 19 Mar 2004 23:15:47 -0500
Cc: "Mohan Parthasarathy" <mohanp@sbcglobal.net>, ipsec@lists.tislabs.com, "Theodore Ts'o" <tytso@mit.edu>
In-reply-to: Your message of "Fri, 19 Mar 2004 20:04:45 EST." <p05200f44bc8144f912eb@[128.89.89.115]>
Reply-to: sommerfeld@east.sun.com
Sender: owner-ipsec@lists.tislabs.com

> 	Well, if we allow this to be any octet string,
> 	then it presents complications for the user/management
> 	interface.  So we'd like to limit it to a text string
> 	containing alphanumeric characters, but not a binary
> 	string, etc.

current best practice for ietf protocols is that strings which are
intended for human display in protocols should come with language
tags.  (why do I know?  sshv2 bit this bullet a while ago...).  see
rfc3066

						- Bill

Follow-Ups:
- Re: Remaining open issues for RFC-2401bis
  - From: Paul Hoffman / VPNC <paul.hoffman@vpnc.org>
- Re: Remaining open issues for RFC-2401bis
  - From: Nicolas Williams <Nicolas.Williams@sun.com>

References:
- Re: Remaining open issues for RFC-2401bis
  - From: Karen Seo <kseo@bbn.com>

Prev by Date: RE: Remaining open issues for RFC-2401bis
Next by Date: Re: Remaining open issues for RFC-2401bis
Previous by thread: RE: Remaining open issues for RFC-2401bis
Next by thread: Re: Remaining open issues for RFC-2401bis
Index(es):
- Date
- Thread