Re: I-D Action: draft-ietf-6man-uri-zoneid-01.txt]
t.petch <ietfc@btconnect.com> Fri, 08 June 2012 14:11 UTC
Return-Path: <ietfc@btconnect.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 0035B21F8929 for <ipv6@ietfa.amsl.com>; Fri, 8 Jun 2012 07:11:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.327
X-Spam-Level:
X-Spam-Status: No, score=-3.327 tagged_above=-999 required=5 tests=[AWL=-0.328, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_LOW=-1]
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 NKHLpH86oMKo for <ipv6@ietfa.amsl.com>; Fri, 8 Jun 2012 07:11:18 -0700 (PDT)
Received: from db3outboundpool.messaging.microsoft.com (db3ehsobe004.messaging.microsoft.com [213.199.154.142]) by ietfa.amsl.com (Postfix) with ESMTP id C8D5921F8927 for <ipv6@ietf.org>; Fri, 8 Jun 2012 07:11:17 -0700 (PDT)
Received: from mail117-db3-R.bigfish.com (10.3.81.228) by DB3EHSOBE003.bigfish.com (10.3.84.23) with Microsoft SMTP Server id 14.1.225.23; Fri, 8 Jun 2012 14:10:25 +0000
Received: from mail117-db3 (localhost [127.0.0.1]) by mail117-db3-R.bigfish.com (Postfix) with ESMTP id 95CB14801ED; Fri, 8 Jun 2012 14:10:25 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.55.224.141; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0702HT002.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -22
X-BigFish: PS-22(zz98dI9371I936eI542M1432I9a6kzz1202hzz1033IL8275bh8275dhz2dh2a8h5a9h668h839h93fhd24hf0ah304l)
Received: from mail117-db3 (localhost.localdomain [127.0.0.1]) by mail117-db3 (MessageSwitch) id 133916462499000_5428; Fri, 8 Jun 2012 14:10:24 +0000 (UTC)
Received: from DB3EHSMHS005.bigfish.com (unknown [10.3.81.248]) by mail117-db3.bigfish.com (Postfix) with ESMTP id 15E993C0254; Fri, 8 Jun 2012 14:10:24 +0000 (UTC)
Received: from DB3PRD0702HT002.eurprd07.prod.outlook.com (157.55.224.141) by DB3EHSMHS005.bigfish.com (10.3.87.105) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 8 Jun 2012 14:10:23 +0000
Received: from DBXPRD0610HT003.eurprd06.prod.outlook.com (157.56.252.181) by pod51017.outlook.com (10.3.4.146) with Microsoft SMTP Server (TLS) id 14.15.74.2; Fri, 8 Jun 2012 14:11:11 +0000
Message-ID: <01e201cd4580$1f1654a0$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <4FC4ED00.5050603@gmail.com> <00df01cd3f08$7b7eacc0$4001a8c0@gateway.2wire.net> <4FC7AA99.1090202@gmail.com>
Subject: Re: I-D Action: draft-ietf-6man-uri-zoneid-01.txt]
Date: Fri, 08 Jun 2012 14:41:31 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.252.181]
X-OriginatorOrg: btconnect.com
Cc: Bob Hinden <bob.hinden@gmail.com>, 6man <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: Fri, 08 Jun 2012 14:11:21 -0000
----- Original Message ----- From: "Brian E Carpenter" <brian.e.carpenter@gmail.com> To: "t.petch" <ietfc@btconnect.com> Cc: "6man" <ipv6@ietf.org>; "Bob Hinden" <bob.hinden@gmail.com> Sent: Thursday, May 31, 2012 6:30 PM > On 2012-05-31 09:36, t.petch wrote: > > Looks good. > > > > I wonder about the first sentence, > > "This document describes how the Zone Identifier of an IPv6 scoped > > address can be represented in a Uniform Resource Identifier that > > includes a literal IPv6 address. " > > > > in that the specification now goes beyond just a literal IPv6 address so > > Where? The only proposal concerns the literal address format (at > least that is the intention). Um, yes. I think I got misled by the word literal; I realise it goes back to RFC2732 but I think I was imagining that there were textual representations that were not literal, whereas the two terms would appear to be synonymous within the context of RFC4007 and this I-D. Tom Petch > > Brian > > > that > > last conditional clause is, while not wrong, perhaps too restrictive, as > > will be clear to anyone who reads on. > > > > Tom Petch > > > > ----- Original Message ----- > > From: "Brian E Carpenter" <brian.e.carpenter@gmail.com> > > To: "6man" <ipv6@ietf.org> > > Cc: "Bob Hinden" <bob.hinden@gmail.com> > > Sent: Tuesday, May 29, 2012 4:36 PM > > Subject: [Fwd: I-D Action: draft-ietf-6man-uri-zoneid-01.txt] > > > > > >> This version favours the option that seemed to get the > >> most positive reaction on the list. There's been quite some > >> restructuring of the draft since the -00 version, so > >> please read it through and send comments. > >> > >> Brian + Bob > >> > >> -------- Original Message -------- > >> Subject: I-D Action: draft-ietf-6man-uri-zoneid-01.txt > >> Date: Tue, 29 May 2012 08:28:15 -0700 > >> From: internet-drafts@ietf.org > >> Reply-To: internet-drafts@ietf.org > >> To: i-d-announce@ietf.org > >> CC: ipv6@ietf.org > >> > >> > >> A New Internet-Draft is available from the on-line Internet-Drafts > > directories. This draft is a work item of the IPv6 > >> Maintenance Working Group of the IETF. > >> > >> Title : Representing IPv6 Zone Identifiers in Uniform > > Resource Identifiers > >> Author(s) : Brian Carpenter > >> Robert M. Hinden > >> Filename : draft-ietf-6man-uri-zoneid-01.txt > >> Pages : 9 > >> Date : 2012-05-29 > >> > >> This document describes how the Zone Identifier of an IPv6 scoped > >> address can be represented in a Uniform Resource Identifier that > >> includes a literal IPv6 address. It updates RFC 3986 and RFC 4007. > >> > >> > >> A URL for this Internet-Draft is: > >> http://www.ietf.org/internet-drafts/draft-ietf-6man-uri-zoneid-01.txt > >> > >> Internet-Drafts are also available by anonymous FTP at: > >> ftp://ftp.ietf.org/internet-drafts/ > >> > >> This Internet-Draft can be retrieved at: > >> ftp://ftp.ietf.org/internet-drafts/draft-ietf-6man-uri-zoneid-01.txt > >> > >> The IETF datatracker page for this Internet-Draft is: > >> https://datatracker.ietf.org/doc/draft-ietf-6man-uri-zoneid/ > >> > >> _______________________________________________ > >> I-D-Announce mailing list > >> I-D-Announce@ietf.org > >> https://www.ietf.org/mailman/listinfo/i-d-announce > >> Internet-Draft directories: http://www.ietf.org/shadow.html > >> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > >> > >> > >> > >> -------------------------------------------------------------------- > >> IETF IPv6 working group mailing list > >> ipv6@ietf.org > >> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > >> -------------------------------------------------------------------- > >> > > > > > > >
- [Fwd: I-D Action: draft-ietf-6man-uri-zoneid-01.t… Brian E Carpenter
- I-D Action: draft-ietf-6man-uri-zoneid-01.txt internet-drafts
- Re: I-D Action: draft-ietf-6man-uri-zoneid-01.txt] t.petch
- Re: I-D Action: draft-ietf-6man-uri-zoneid-01.txt] Brian E Carpenter
- Re: I-D Action: draft-ietf-6man-uri-zoneid-01.txt] t.petch