draft-chown-6man-tokenised-ipv6-identifiers-02

Tim Chown <tjc@ecs.soton.ac.uk> Mon, 05 November 2012 16:18 UTC

Return-Path: <tjc@ecs.soton.ac.uk>
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 421CC21F841A for <ipv6@ietfa.amsl.com>; Mon, 5 Nov 2012 08:18:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6nL1wC7U0CGT for <ipv6@ietfa.amsl.com>; Mon, 5 Nov 2012 08:18:23 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 63D8221F85BA for <ipv6@ietf.org>; Mon, 5 Nov 2012 08:18:23 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id qA5GID1v009647 for <ipv6@ietf.org>; Mon, 5 Nov 2012 16:18:13 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk qA5GID1v009647
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1352132293; bh=ClsavBidfnf7yVqnm/Pi/DfkJms=; h=From:Subject:Date:To:Mime-Version:References; b=2OPKjlXkOkGyj5jQ8nLWAv6dUK+eHLe4dRjSxGh+7giOGTo3LAU8XvyQd6V6ebQWq HlzLERUZcNx5j7/3naX1OurKG9w8aZaBU/wp188mjSqPNCooo6s1vV0RxK7eXA11RO ZcZtbNyfxz+9qA5vjHsShU36UvGaKullLuwxSM8Y=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id oA4GID0430657178i8 ret-id none; Mon, 05 Nov 2012 16:18:13 +0000
Received: from tjc-vpn.ecs.soton.ac.uk (tjc-vpn.ecs.soton.ac.uk [152.78.236.241]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id qA5GIA2R025916 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ipv6@ietf.org>; Mon, 5 Nov 2012 16:18:11 GMT
From: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: multipart/alternative; boundary="Apple-Mail=_A6F75255-00B9-4817-8FA8-569D8B629412"
Subject: draft-chown-6man-tokenised-ipv6-identifiers-02
Message-ID: <EMEW3|882e9906ce6013fc4615a05054af7019oA4GID03tjc|ecs.soton.ac.uk|4095A217-29D5-41E8-B6D3-F5AE51F3E931@ecs.soton.ac.uk>
Date: Mon, 05 Nov 2012 16:18:10 +0000
To: IPv6 List <ipv6@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=oA4GID043065717800; tid=oA4GID0430657178i8; client=relay,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
References: <4095A217-29D5-41E8-B6D3-F5AE51F3E931@ecs.soton.ac.uk>
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: qA5GID1v009647
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
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: Mon, 05 Nov 2012 16:18:24 -0000

Hi,

I forgot to ask for a 5 min slot for this in Atlanta.

http://tools.ietf.org/html/draft-chown-6man-tokenised-ipv6-identifiers-02

The draft describes a way to simplify (a little!) server renumbering in SLAAC networks.  Rather than manually configuring a 128-bit address on servers, you configure the 64-bit interface identifier, and rely on the RA to learn the prefix.

There was an implementation for Solaris, and a patch for Linux many years ago,

Is there interest in promoting this idea further, and importantly any IPR preventing doing so?  Or is there reluctance from admins to rely on RAs to configure a full server IPv6 address?

Tim