[6lo] FW: New Version Notification for draft-ietf-6lo-backbone-router-11.txt

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Mon, 04 February 2019 12:15 UTC

Return-Path: <pthubert@cisco.com>
X-Original-To: 6lo@ietfa.amsl.com
Delivered-To: 6lo@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6052D128766; Mon, 4 Feb 2019 04:15:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -19.054
X-Spam-Level:
X-Spam-Status: No, score=-19.054 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 rPqq7qJ0ZOKQ; Mon, 4 Feb 2019 04:15:48 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 50AA21277BB; Mon, 4 Feb 2019 04:15:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2752; q=dns/txt; s=iport; t=1549282548; x=1550492148; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=4LPL2P2hwklhLPdlekmmjJZaAVmuYIJNROToYHR7X+Y=; b=AGDyT85QlY7sFy+Wird/2H2CGEazDcQCtfyw6wcxZnAgGxsU5LdwyLKu pLjj98gmpPz8OjS9/zH3T0woxyZyVaPskjzAKrLJ1pBqhmb1JBm/Of4lE pOohFrHlpQwVUG0Frge+WYnV3k2dckdaBfRDzGeNtywDicG8za4bh3eOT I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ADAADqK1hc/4oNJK1kGQEBAQEBAQEBAQEBAQcBAQEBAQGBUQQBAQEBAQsBggNngQMnCoN5iBqLc4INmA8UgWcLAQElhEcCF4MEIjQJDQEDAQECAQECbRwBC4VKAQEBBCMRQwIMBAIBCBEEAQEDAiYCAgIwFQYBAQUDAgQOBQiDG4IBD6l8gS+EMwIOQYUkgQuLNheBQD+BEYMSgx4BAQIBARaBD4NBglcCkCySRgkChzCDYYFihT0hgWxShG+LF4ojhS+MBgIRFIEnHziBVnAVGoMNCYIfF4hfhT9BMQGNWYEfAQE
X-IronPort-AV: E=Sophos;i="5.56,560,1539648000"; d="scan'208";a="512690857"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Feb 2019 12:15:46 +0000
Received: from XCH-RCD-002.cisco.com (xch-rcd-002.cisco.com [173.37.102.12]) by alln-core-5.cisco.com (8.15.2/8.15.2) with ESMTPS id x14CFkF5016410 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 4 Feb 2019 12:15:46 GMT
Received: from xch-rcd-001.cisco.com (173.37.102.11) by XCH-RCD-002.cisco.com (173.37.102.12) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 4 Feb 2019 06:15:46 -0600
Received: from xch-rcd-001.cisco.com ([173.37.102.11]) by XCH-RCD-001.cisco.com ([173.37.102.11]) with mapi id 15.00.1395.000; Mon, 4 Feb 2019 06:15:46 -0600
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "6lo@ietf.org" <6lo@ietf.org>
CC: "draft-ietf-6lo-backbone-router@ietf.org" <draft-ietf-6lo-backbone-router@ietf.org>
Thread-Topic: New Version Notification for draft-ietf-6lo-backbone-router-11.txt
Thread-Index: AQHUvIIbX8zsACv0HkiM3WMH40lxqqXPi/pA
Date: Mon, 04 Feb 2019 12:15:17 +0000
Deferred-Delivery: Mon, 4 Feb 2019 12:14:50 +0000
Message-ID: <47b101a513a64b69820003e0a36e0418@XCH-RCD-001.cisco.com>
References: <154928200791.22885.473974996457845996.idtracker@ietfa.amsl.com>
In-Reply-To: <154928200791.22885.473974996457845996.idtracker@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.55.22.4]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.37.102.12, xch-rcd-002.cisco.com
X-Outbound-Node: alln-core-5.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/sOzBMJXZIapCLmwivr6PQG0WfYM>
Subject: [6lo] FW: New Version Notification for draft-ietf-6lo-backbone-router-11.txt
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Mailing list for the 6lo WG for Internet Area issues in IPv6 over constrained node networks." <6lo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6lo>, <mailto:6lo-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6lo/>
List-Post: <mailto:6lo@ietf.org>
List-Help: <mailto:6lo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lo>, <mailto:6lo-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Feb 2019 12:15:50 -0000

Dear all:

The main comment we got during WGLC was that we did not indicate that the 6LBR on the backbone can be used later for lookup operations.
This was clarified with new text and a pointer to the 6lo-unicast-lookup draft.

Carles: I think the document is ready for publication. 

All the best,

Pascal

-----Original Message-----
From: internet-drafts@ietf.org <internet-drafts@ietf.org> 
Sent: lundi 4 février 2019 13:07
To: Pascal Thubert (pthubert) <pthubert@cisco.com>; Charles E. Perkins <charliep@computer.org>; Eric Levy- Abegnoli (elevyabe) <elevyabe@cisco.com>; Charles Perkins <charliep@computer.org>
Subject: New Version Notification for draft-ietf-6lo-backbone-router-11.txt


A new version of I-D, draft-ietf-6lo-backbone-router-11.txt
has been successfully submitted by Pascal Thubert and posted to the IETF repository.

Name:		draft-ietf-6lo-backbone-router
Revision:	11
Title:		IPv6 Backbone Router
Document date:	2019-02-04
Group:		6lo
Pages:		30
URL:            https://www.ietf.org/internet-drafts/draft-ietf-6lo-backbone-router-11.txt
Status:         https://datatracker.ietf.org/doc/draft-ietf-6lo-backbone-router/
Htmlized:       https://tools.ietf.org/html/draft-ietf-6lo-backbone-router-11
Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-6lo-backbone-router
Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-6lo-backbone-router-11

Abstract:
   This document updates RFC 4861 and RFC 8505 in order to enable proxy
   services for IPv6 Neighbor Discovery by Routing Registrars called
   Backbone Routers.  Backbone Routers are placed along the wireless
   edge of a Backbone, and federate multiple wireless links to form a
   single MultiLink Subnet.

                                                                                  


Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat