IETF Logo Mail Archive

Re: Character set for Line ID

Suresh Krishnan <suresh.krishnan@ericsson.com> Thu, 08 December 2011 05:39 UTC

Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C4B721F84FB for <ipv6@ietfa.amsl.com>; Wed, 7 Dec 2011 21:39:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.107
X-Spam-Level:
X-Spam-Status: No, score=-106.107 tagged_above=-999 required=5 tests=[AWL=0.492, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yELQR4nQb1ed for <ipv6@ietfa.amsl.com>; Wed, 7 Dec 2011 21:39:43 -0800 (PST)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id F08AD21F84FA for <ipv6@ietf.org>; Wed, 7 Dec 2011 21:39:42 -0800 (PST)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id pB85dbY5022082 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 7 Dec 2011 23:39:40 -0600
Received: from [164.48.125.41] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.181) with Microsoft SMTP Server (TLS) id 8.3.137.0; Thu, 8 Dec 2011 00:39:36 -0500
Message-ID: <4EE04D22.3050702@ericsson.com>
Date: Thu, 08 Dec 2011 00:37:38 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: RJ Atkinson <rja.lists@gmail.com>
Subject: Re: Character set for Line ID
References: <EAC60EFC-0411-48AE-92D1-7621DCA60CA1@gmail.com>
In-Reply-To: <EAC60EFC-0411-48AE-92D1-7621DCA60CA1@gmail.com>
X-Enigmail-Version: 1.3.3
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Dec 2011 05:39:44 -0000

Hi Ran,
  Thanks for the explanation. It was very useful.

On 12/06/2011 02:35 PM, RJ Atkinson wrote:
> 
> Bob,
> 
>   My read of the relevant RFCs is that the 
> DHCP Line-ID option specifies the use of the "NVT"
> character set.  
> ...
> Now, if one's goal is *strict* compatibility with
> the DHCP Line-ID option, then the NVT character
> set (originally specified in very early RFCs)
> ought to be specified.  

This is not a goal but is certainly a limiting factor. I have checked
with a few BBF operators and they believe that the printable subset of
7-bit ASCII should be sufficient to hold the line ids. From my reading
of RFC854 (is there a more specific reference?) it seems that NVT should
be able to hold all possible line-ids.

Thanks
Suresh

v2.23.0 | Report a Bug | By Email