Re: [Softwires] [Technical Errata Reported] RFC5969 (3049)

"Hemant Singh (shemant)" <shemant@cisco.com> Sun, 11 December 2011 17:13 UTC

Return-Path: <shemant@cisco.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 656AF21F845B for <softwires@ietfa.amsl.com>; Sun, 11 Dec 2011 09:13:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.518
X-Spam-Level:
X-Spam-Status: No, score=-6.518 tagged_above=-999 required=5 tests=[AWL=0.081, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 i6iadHfQHo+V for <softwires@ietfa.amsl.com>; Sun, 11 Dec 2011 09:13:47 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 9E16721F8457 for <softwires@ietf.org>; Sun, 11 Dec 2011 09:13:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shemant@cisco.com; l=3008; q=dns/txt; s=iport; t=1323623627; x=1324833227; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=6b1STtg7EABIzniVj/HJlUjKmcEEceTExGFVkwd/lBY=; b=FM346EIJ2bSri0l1tnuw3QQOCTqW2TwtlDYogCFx2WacN2Is9JtaYOeG m3Y+uqIwSQKSeLT3IdeFZySks7rn62qeGW9b3v8Op/pE8UEEvzQk+faAR xO9p15CK5fFnCQ4OL0cKuj4rV4A6vgaEm5sotFTPbRWM3xkKfhBbGquiq k=;
X-IronPort-AV: E=Sophos;i="4.71,335,1320624000"; d="scan'208";a="42976465"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-1.cisco.com with ESMTP; 11 Dec 2011 17:13:47 +0000
Received: from xbh-rcd-101.cisco.com (xbh-rcd-101.cisco.com [72.163.62.138]) by rcdn-core-6.cisco.com (8.14.3/8.14.3) with ESMTP id pBBHDlpB008088; Sun, 11 Dec 2011 17:13:47 GMT
Received: from xmb-rcd-109.cisco.com ([72.163.62.151]) by xbh-rcd-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Sun, 11 Dec 2011 11:13:47 -0600
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 11 Dec 2011 11:13:45 -0600
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C3038294B5@XMB-RCD-109.cisco.com>
In-Reply-To: <20111211151333.5234D72E004@rfc-editor.org>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Softwires] [Technical Errata Reported] RFC5969 (3049)
Thread-Index: Acy4F5Lp+hAJiv9VTYykrK4sfNY87wADrQRQ
References: <20111211151333.5234D72E004@rfc-editor.org>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: RFC Errata System <rfc-editor@rfc-editor.org>, mark@townsley.net, ot@cisco.com, rdroms.ietf@gmail.com, jari.arkko@piuha.net, adurand@juniper.net, cuiyong@tsinghua.edu.cn
X-OriginalArrivalTime: 11 Dec 2011 17:13:47.0032 (UTC) FILETIME=[3E4CB980:01CCB828]
Cc: softwires@ietf.org, alessandro.cortiana@gmail.com
Subject: Re: [Softwires] [Technical Errata Reported] RFC5969 (3049)
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Dec 2011 17:13:48 -0000

While we are on the subject of Errata in RFC 5969, aren't the following
two pieces of text from RFC 5969 inconsistent?

[In 6rd, all CEs and BRs can be considered as connected to the same
virtual link and therefore neighbors to each other.]

[with all 6rd CEs and BRs defined as off-link neighbors from one other.]

There is no such thing as an off-link neighbor - a neighbor, by
definition is on the same link.  Maybe I have a nitpick, but certainly
some better text could be uses because off-link vs. on-link has specific
rules for when to issues an NS or not.  

Hemant

-----Original Message-----
From: softwires-bounces@ietf.org [mailto:softwires-bounces@ietf.org] On
Behalf Of RFC Errata System
Sent: Sunday, December 11, 2011 10:14 AM
To: mark@townsley.net; ot@cisco.com; rdroms.ietf@gmail.com;
jari.arkko@piuha.net; adurand@juniper.net; cuiyong@tsinghua.edu.cn
Cc: softwires@ietf.org; alessandro.cortiana@gmail.com;
rfc-editor@rfc-editor.org
Subject: [Softwires] [Technical Errata Reported] RFC5969 (3049)


The following errata report has been submitted for RFC5969,
"IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) -- Protocol
Specification".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=5969&eid=3049

--------------------------------------
Type: Technical
Reported by: Alessandro Cortiana <alessandro.cortiana@gmail.com>

Section: 12

Original Text
-------------
By restricting the 6rd domain to within a provider
network, a CE only needs to accept packets from a single or small set
of known 6rd BR IPv4 addresses.

Corrected Text
--------------
By restricting the 6rd domain to within a provider
network, a CE only needs to accept packets from a single or small set
of known 6rd BR IPv4 addresses and from other CEs within the 6rd domain.

Notes
-----
A CE also needs to accept packets from other CEs within the 6rd domain.
This happens when, within a 6rd domain, two customer sites want to
communicate.
Reference: RFC5569 section 3

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC5969 (draft-ietf-softwire-ipv6-6rd-10)
--------------------------------------
Title               : IPv6 Rapid Deployment on IPv4 Infrastructures
(6rd) -- Protocol Specification
Publication Date    : August 2010
Author(s)           : W. Townsley, O. Troan
Category            : PROPOSED STANDARD
Source              : Softwires
Area                : Internet
Stream              : IETF
Verifying Party     : IESG
_______________________________________________
Softwires mailing list
Softwires@ietf.org
https://www.ietf.org/mailman/listinfo/softwires