[lisp] Editorial error in RFC 6830
"Victor Moreno (vimoreno)" <vimoreno@cisco.com> Fri, 23 October 2015 18:34 UTC
Return-Path: <vimoreno@cisco.com>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B557E1A1B1B for <lisp@ietfa.amsl.com>; Fri, 23 Oct 2015 11:34:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hun_0c1BZj9A for <lisp@ietfa.amsl.com>; Fri, 23 Oct 2015 11:34:44 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B641B1A007C for <lisp@ietf.org>; Fri, 23 Oct 2015 11:34:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=471; q=dns/txt; s=iport; t=1445625284; x=1446834884; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=Laug9kTggNcGIIjFNV7HQ+T8bdlSJZaYFWut00yLJdk=; b=gXukXPsNwkZeuuNGwIgvX6h4jGAa0R9nw7rdDSicHzFYNoJ/U+cDj4Da 2kedq9VNKjSHPei9HhIhr7vOn9NQp65qKR573usTep5EY0M1wqfog1dam iRObsN2IJuATjcvD/jihMyisVMDFwiwcvL4parQYy/gFKK7VZvNKmh577 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D3AQCvfCpW/5xdJa1egzaBSb4mAQ2BWYdeOBQBAQEBAQEBgQqEOTpRAT5CJwSIQ6Nfok0BAQEBAQUBAQEBAQEBARuGd4IQhCuGcYEUBZYrAXmMJJwlAR8BAUKCHoFlhi+BBgEBAQ
X-IronPort-AV: E=Sophos;i="5.20,187,1444694400"; d="scan'208";a="38496954"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-9.cisco.com with ESMTP; 23 Oct 2015 18:34:43 +0000
Received: from XCH-ALN-013.cisco.com (xch-aln-013.cisco.com [173.36.7.23]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id t9NIYh5E019965 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <lisp@ietf.org>; Fri, 23 Oct 2015 18:34:44 GMT
Received: from xch-rcd-015.cisco.com (173.37.102.25) by XCH-ALN-013.cisco.com (173.36.7.23) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Fri, 23 Oct 2015 13:34:22 -0500
Received: from xch-rcd-015.cisco.com ([173.37.102.25]) by XCH-RCD-015.cisco.com ([173.37.102.25]) with mapi id 15.00.1104.000; Fri, 23 Oct 2015 13:34:22 -0500
From: "Victor Moreno (vimoreno)" <vimoreno@cisco.com>
To: LISP mailing list list <lisp@ietf.org>
Thread-Topic: Editorial error in RFC 6830
Thread-Index: AQHRDcFvm1CW0pE9zUWBJGdstXRtHg==
Date: Fri, 23 Oct 2015 18:34:22 +0000
Message-ID: <6A4EB81B-2780-4A19-B22D-55A048B2E5FB@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.204.179]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <0950B26ADDDBFF479E516FDA8BAA7844@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/lisp/icWMZyN8qyPeK46Md4-Ev93CWkc>
Subject: [lisp] Editorial error in RFC 6830
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lisp>, <mailto:lisp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lisp/>
List-Post: <mailto:lisp@ietf.org>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Oct 2015 18:34:45 -0000
Hello WG, I found the following editorial error, I understand text fixes to the RFC are currently being collected. Negative mapping entries are introduced in section 3 (page 8) and therein is a cross-reference to section 6.1.5 for the well defined actions associated with a negative map reply. The cross referenced actions are actually documented in section 6.1.4, not 6.1.5. The cross-reference needs to be corrected to 6.1.4. Regards, -v
- [lisp] Editorial error in RFC 6830 Victor Moreno (vimoreno)