[OSPF] Fw: Last Call: <draft-ietf-ospf-rfc4970bis-04.txt> (Extensions to OSPF for Advertising Optional Router Capabilities) to Proposed Standard

t.petch <ietfc@btconnect.com> Fri, 25 September 2015 07:36 UTC

Return-Path: <ietfc@btconnect.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A1891ACDC1 for <ospf@ietfa.amsl.com>; Fri, 25 Sep 2015 00:36:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001] 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 e6ZD2nmwutJJ for <ospf@ietfa.amsl.com>; Fri, 25 Sep 2015 00:36:19 -0700 (PDT)
Received: from emea01-db3-obe.outbound.protection.outlook.com (mail-db3on0734.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe04::734]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E3C81B31B2 for <ospf@ietf.org>; Fri, 25 Sep 2015 00:36:19 -0700 (PDT)
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=ietfc@btconnect.com;
Received: from pc6 (31.54.179.163) by DB3PR07MB058.eurprd07.prod.outlook.com (10.242.137.148) with Microsoft SMTP Server (TLS) id 15.1.274.16; Fri, 25 Sep 2015 07:36:00 +0000
Message-ID: <004c01d0f764$d1effa60$4001a8c0@gateway.2wire.net>
From: t.petch <ietfc@btconnect.com>
To: <ospf@ietf.org>
Date: Fri, 25 Sep 2015 08:35:51 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
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: [31.54.179.163]
X-ClientProxiedBy: HE1PR05CA0036.eurprd05.prod.outlook.com (25.162.181.46) To DB3PR07MB058.eurprd07.prod.outlook.com (10.242.137.148)
X-Microsoft-Exchange-Diagnostics: 1; DB3PR07MB058; 2:eZcpXaz7677YSf41FQ9wt/KFU6zta+CBpDefu/0VS9+6EtWlI+Dotoku62p9qY8ainD6hhwZqf1nVYUsVn52gUmhxfDjhGYW0uHx7K1n06X6jCLc7clMxmNnXLVz/Z+R4VJfcp4HHwvXWqR+hqWQzGTaYbFUB84ve9Wgi6aY4NY=; 3:Xre3PNjDAPoLW2+KW6kMoUH3pPQa52DJGhBH4bKml6E1FNdBSDBz1/yL47ptcI6TRlVPi8EmW2FYmrIYU9494KZ5YWewYvCECIp1FXuZEiy6e0l2mtfD/kA3Fc+4GZWOo8T8SnjU/uaMnhmIzK1HjA==; 25:GwvHb4qsjQ4ZaIsqvYFWmPlk6gsXrQV/BJuoyr8s5fVdbrp2rE2qEnyqZWZ7Osi6jPUHDZaeuN4fu5k+vSzjinaiqxObCeGrLwERDWiJk09WiCqrj+KgF+A6+5ZmCh7ybllQYow3XtgGhuMBrL0+mLaEzF/v+n70hmL/rfef+1XAMIY3Z3UYkoZd1vrHSvYENv4bdUeUe3JfhN1YNfWON+baO9YMN74/EHSO2vPcWg6FrXxGQP6QejT/i5RdhNbK/bkJl9EXmdosx+TwdAjX0Q==
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DB3PR07MB058;
X-Microsoft-Antispam-PRVS: <DB3PR07MB05892373E9DFDE8F9ADDA2CA0420@DB3PR07MB058.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(2401047)(520078)(5005006)(8121501046)(3002001); SRVR:DB3PR07MB058; BCL:0; PCL:0; RULEID:; SRVR:DB3PR07MB058;
X-Microsoft-Exchange-Diagnostics: 1; DB3PR07MB058; 4:SRLFoL+wqbZSxgEwHUishwJmo6QGS11iZ5/ln7v4UUsF1j1jCmsB8Vv6C/Tjx9oG4lp5zpyDU3ApP0dSo/UlX1l5J6n2NVok52Qh6YFovRuCU+3AvZ+Us2BVDbvzRNN3zQ45yt9NcQ5LFGk5JQL+kV2paKcG+vMXBlfg/70uh4xdD27beYKSJonDbom1eU+MbBTovwqrx9mQOW/4UYJErrJrR5E5jesTzRw3FsKYS1UzbZPEp/p+f58WjE9yWSSZcLD7hVrwMMe0bzgPRJ+eSo0tYU7hhkFYBPjG2kY3I7Y5NTI9Ap/GtySkGirL7uHCYrGF5UhMHN+xC/yvIuGsshAivTw/uLMIc/xnrsqfD/A=
X-Forefront-PRVS: 07106EF9B9
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(6009001)(377454003)(189002)(13464003)(199003)(1556002)(92566002)(5007970100001)(107886002)(5001960100002)(4001540100001)(97736004)(81156007)(5004730100002)(86362001)(116806002)(122386002)(50466002)(87976001)(40100003)(110136002)(230783001)(5001860100001)(189998001)(84392001)(50226001)(66066001)(44736004)(5001830100001)(42186005)(64706001)(47776003)(14496001)(5001920100001)(1456003)(81686999)(81816999)(46102003)(77096005)(19580405001)(61296003)(44716002)(62966003)(33646002)(101416001)(68736005)(77156002)(15975445007)(19580395003)(106356001)(2351001)(450100001)(23756003)(62236002)(105586002)(50986999)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB3PR07MB058; H:pc6; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:0; LANG:en;
Received-SPF: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?iso-8859-1?Q?1; DB3PR07MB058; 23:Ae28PYJsdmz8wP3bfNEbiAZF+ZcRUj8f9AmWghax?= =?iso-8859-1?Q?MZuDHUMq1aEkeKp8Oi3qVj1wN3AGbvXQ9Lj44/D5HUFjQh/YC58ccqjSuQ?= =?iso-8859-1?Q?bowHaCJ4wj7jtxnB2Jwvm4mwMIUJypb9jXQmMsm0akN/pvNM3RQfARcOWf?= =?iso-8859-1?Q?mjGGxZSs6guS/tu4i54NYptBkdZGrf2uCd7V4yzxSFpXcVnq+IGWmSrK/2?= =?iso-8859-1?Q?m26PEqAoeXpyRn5S0a/IbPqR4Cd9px3AwdlHRK3uUyKSbnJjFSMQ6p/9c9?= =?iso-8859-1?Q?GYYdJgt+pimSF0nsB1KHck1ZZiH4faEU9iPBtFM0GvfFFB/3KIdNm90U1/?= =?iso-8859-1?Q?VWFHfwGlDBWh/KhEyUAHqH92DZy3NKiSOeYrMEZXLwDC6hKq/jsx4X76zj?= =?iso-8859-1?Q?SxyF/UXpdtcU1i91GdQMRBUKL56b1IT29IAGoyUGYd9yKW5LvlZyla44et?= =?iso-8859-1?Q?cKHQ/ItuLGKyT79fTe46Oo2ZqhuEre6auXkSpZNNaVBh4YJnm9nozBZZ/C?= =?iso-8859-1?Q?T0ANyq+yy3SV/azkj1Lw1oGD92ss7dbOnhS6W+A9vqnGWKSbRBynRqeMzv?= =?iso-8859-1?Q?8l3AzzlVFtwGMXyWQkqEpUO1QrCXN7VnLAK0+9f75vWM/2CUnyrtT7I7g7?= =?iso-8859-1?Q?Tv5fU29MMSrLAnT5Vu9Abpe/w+7UEhV/0pR66aOIYTX3LV7Vs7QG/rJmkc?= =?iso-8859-1?Q?c+DxhamBBz+Ajj0wUU0sJsNcuE0H7QGwzEbMF94O1Z95L2YYk3V5fhhe3Y?= =?iso-8859-1?Q?kRlCtmQVIch8LOiLNbFVCxk6+6IHtHyqxzs6He6FLC4sCh/Ti+7xAsjB55?= =?iso-8859-1?Q?y299xSOviG3VNUUGT4YFpeJ77Cqp0zQ/5a1ML7zIeTBc5+0n3+3XHCzF+5?= =?iso-8859-1?Q?r4feAt00cBe/k1ZbAyHX2V8QyZlOgzR9lWO5o2qRwO1/I3ZxPwkNg7YTDg?= =?iso-8859-1?Q?3XCUIwzSpLwCxwjEnmwSENgyv0KoVuRZbCRCP9z+Re4jrRj4lDXlxl+DJ1?= =?iso-8859-1?Q?wo5vcgB0i9zt4WVbg0M1kP/xyc3e/JuhXhSZt/PE4oKoPxNppKcnog2Edh?= =?iso-8859-1?Q?u4tJ6mA2848b4UrB9HY0N7+iG2XjrDop/tMxWe5E6KD519RxYdbxeMABcp?= =?iso-8859-1?Q?3yhwy5iXCtdfPF7YKnFxQ5zF8H/EgbgpDtzb9wpcgrjmfUJe34/VyWpq8E?= =?iso-8859-1?Q?Klr6B6tAQ69Vj3IyDb4zXyxB/g6OZ20A7ouL2eh3bJSqr9kqfp1VQMWxwB?= =?iso-8859-1?Q?d9aVQXDTlAvwyaWwves1oFjN4OEXvANHNJMZhZK5c232rVhiHcKuIrqx1Q?= =?iso-8859-1?Q?r5YPQCqyomqJhZv8mBrT7YANa9P9W8/Rfxjw/yywLESlPoLihgLJBa9UDL?= =?iso-8859-1?Q?f83PhyUmAP90KFuIBMboObFr0xBM0+rNieuxojCBY6yFbDx0E43UXGsVnU?= =?iso-8859-1?Q?IvJDwOODdkxhAIGaNSF1Ts3M1c2nxJSQhh5usmshe7E8nmus73kLghzObI?= =?iso-8859-1?Q?qfRpZudN+rtcEcTRo6476AwNGwuDCQt28fqh2hNbkiccp3uIoYmmRqynyB?= =?iso-8859-1?Q?qfbw=3D=3D?=
X-Microsoft-Exchange-Diagnostics: 1; DB3PR07MB058; 5:6wWao+7PXNgEmU6hA8RsrlfhzhkeCFvrR7orfDu+/VEMoou01nOsR/5YEjzdlL8ggl9JEOQvNJOuPV/vh3Tpf4GHeIxfDyTChJ5at+/HI+wp7CB/kkUlOXi2URVQMpKXdbooMFyZG48IQQKfFiProg==; 24:ZpDI8AsCKI0vtmEjNE1SPBQ/63zLN7iDEWacka/ocLazGB8TBi72X/kgRrFpiBhjedXDCV1TioPJD+JkweyZEdjwZfwGQA6SUR+sGduufS8=; 20:Yz38jeXP0vq6bLmXMLbgLJqcacSt8suBHzFKdnMTq0tQh8N4m6TT4bOjqJdlqrgS4hS1aPR0oJVK8OkVPcQUJQ==
SpamDiagnosticOutput: 1:23
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 25 Sep 2015 07:36:00.8074 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB3PR07MB058
Archived-At: <http://mailarchive.ietf.org/arch/msg/ospf/DzsVJTVczuF0o0rXLdzvMhqqmOc>
Subject: [OSPF] Fw: Last Call: <draft-ietf-ospf-rfc4970bis-04.txt> (Extensions to OSPF for Advertising Optional Router Capabilities) to Proposed Standard
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ospf/>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Sep 2015 07:36:22 -0000

Acee

As requested.

Tom Petch


----- Original Message -----
From: "t.p." <daedulus@btconnect.com>
To: "ietf" <ietf@ietf.org>
Sent: Friday, September 25, 2015 8:34 AM
Subject: Re: Last Call: <draft-ietf-ospf-rfc4970bis-04.txt> (Extensions
to OSPF for Advertising Optional Router Capabilities) to Proposed
Standard


> I find the IANA Considerations of this I-D most unclear.  What I think
> they are trying to say is
>
> NEW
>
> 5.  IANA Considerations
>
> 5.1
> [RFC4970] defined the Router Information opaque LSA as type 4 in the
> Opaque Link-State Advertisements (LSA) Option Types Registry.  IANA is
> asked to update the reference for that entry to point to this RFC.
>
> 5.2
>
> [RFC4970] created the registry for OSPFv3 LSA Function Codes.  IANA is
> requested to update the reference for that registry to point to this
> RFC.  References within that registry to [RFC4970] should be updated
to
> point to this RFC; references to other RFCs are unchanged.  The
> definition and assignment policy has been updated as follows.
>
> This registry  is now comprised of the fields Value, LSA function code
> name,
>        and Document Reference.  The OSPFv3 LSA function code is
defined
>        in section A.4.2.1 of [OSPFV3].  The OSPFv3 LSA function code
12
>        has been reserved for the OSPFv3 Router Information (RI) LSA.
>
>
>
+-----------+-------------------------------------+
>                      | Range     | Assignment Policy
|
>
+-----------+-------------------------------------+
>                      | 0         | Reserved (not to be assigned)
|
>                      |           |
|
>                      | 1-11      | Already assigned
|
>                      |           |
|
>                      | 12        | OSPFv3 RI LSA (Assigned herein)
|
>                      |           |
|
>                      | 13-15     | Already assigned
|
>                      |           |
|
>                      | 16-255    | Unassigned (IETF Review)
|
>                      |           |
|
>                      | 256-8175  | Reserved (No assignments)
|
>                      |           |
|
>                      | 8176-8183 | Experimentation (No assignments)
|
>                      |           |
|
>                      | 8184-8191 | Vendor Private Use (No assignments)
|
>
+-----------+-------------------------------------+
>
>                          OSPFv3 LSA Function Codes
>
>        *  OSPFv3 LSA function codes in the range 16-255 are not be
>           assigned subject to IETF Review.  New values are assigned
only
>           through RFCs that have been shepherded through the IESG as
AD-
>           Sponsored or IETF WG Documents [IANA-GUIDE].
>
>        *  OSPFv3 LSA function codes in the range 8176-8181 are for
>           experimental use; these will not be registered with IANA and
>           MUST NOT be mentioned by RFCs.
>
>        *  OSPFv3 LSAs with an LSA Function Code in the Vendor Private
>           Use range 8184-8191 MUST include the Vendor Enterprise Code
as
>           the first 4 octets following the 20 octets of LSA header.
>
>        *  If a new LSA Function Code is documented, the documentation
>           MUST include the valid combinations of the U, S2, and S1
bits
>           for the LSA.  It SHOULD also describe how the Link State ID
is
>           to be assigned.
>
> 5.3
>
> [RFC4970] created the registry for OSPF Router Information (RI) TLVs.
> IANA is requested to update the reference for this registry to point
to
> this RFC.  The definition and assignment policy has been updated as
> follows.  References within that registry to [RFC4970] should be
updated
> to point to this RFC; references to other RFCs are unchanged.  The
> definition and assignment policy has been updated as follows.
>
>
> The registry is now comprised of the fields Value, TLV Name, and
> Document Reference.
>        The value of 1 for the informational capabilities TLV is
defined
>        herein.  The value IANA TBD (suggested value 2) for the Router
>        Functional Capabilities TLV is also defined herein.
>
>
>
+-------------+-----------------------------------+
>                      | Range       | Assignment Policy
|
>
+-------------+-----------------------------------+
>                      | 0           | Reserved (not to be assigned)
|
>                      |             |
|
>                      | 1           | Informational Capabilities
|
>                      |             |
|
>                      | 2           | Unassigned (IETF Review)
|
>                      |             |
|
>                      | TBD         | Functional Capabilities
|
>                      |             |
|
>                      | 3-9         | Already Assigned
|
>                      |             |
|
>                      | 10-32767    | Unassigned (IETF Review)
|
>                      |             |
|
>                      | 32768-32777 | Experimentation (No assignments)
|
>                      |             |
|
>                      | 32778-65535 | Reserved (Not to be assigned)
|
>
+-----------+-------------------------------------+
>
>                                OSPF RI TLVs
>
>        *  Types in the range 2, 10-32767 are to be assigned subject to
>           IETF Review.  New values are assigned only through RFCs that
>           have been shepherded through the IESG as AD-Sponsored or
IETF
>           WG Documents [IANA-GUIDE].
>
>        *  Types in the range 32778-65535 are reserved and are not to
be
>           assigned at this time.  Before any assignments can be made
in
>           this range, there MUST be a Standards Track RFC that
specifies
>           IANA Considerations that covers the range being assigned.
>
>
> 5.4
>
> [RFC4970] created the registry for  OSPF Router Informational
Capability
> Bits.  IANA is requested to update the reference for this registry to
> point to this RFC.  The definition and assignment policy has been
> updated as follows.
>
>  - This registry is now comprised of the
>        fields Bit Number, Capability Name, and Document Reference.
The
>        values are defined in Section 2.4.  All Router Informational
>        Capability TLV additions are to be assigned through IETF
Review.
>
>
> 5.5
>
> IANA ia asked to create a registry for OSPF Router Functional
Capability
> Bits within the Open Shortest Path First v2 (OSPFv2) Parameters
Group.
>
> This registry will be comprised of the
>        fields Bit Number, Capability Name, and Document Reference.
>        Initially, the sub-registry will be empty but will be available
>        for future capabilities.  All Router Functional Capability TLV
>        additions are to be assigned through IETF Review.
>
>
> </NEW>
>
> but I could be wrong!
>
>
> Tom Petch
>
>
> ----- Original Message -----
> From: "The IESG" <iesg-secretary@ietf.org>
> To: "IETF-Announce" <ietf-announce@ietf.org>
> Cc: <ospf@ietf.org>
> Sent: Friday, September 25, 2015 1:40 AM
> Subject: [OSPF] Last Call: <draft-ietf-ospf-rfc4970bis-04.txt>
> (Extensions to OSPF for Advertising Optional Router Capabilities) to
> Proposed Standard
>
>
> >
> > The IESG has received a request from the Open Shortest Path First
IGP
> WG
> > (ospf) to consider the following document:
> > - 'Extensions to OSPF for Advertising Optional Router Capabilities'
> >   <draft-ietf-ospf-rfc4970bis-04.txt> as Proposed Standard
> >
> > The IESG plans to make a decision in the next few weeks, and
solicits
> > final comments on this action. Please send substantive comments to
the
> > ietf@ietf.org mailing lists by 2015-10-08. Exceptionally, comments
may
> be
> > sent to iesg@ietf.org instead. In either case, please retain the
> > beginning of the Subject line to allow automated sorting.
> >
> > Abstract
> >
> >
> >    It is useful for routers in an OSPFv2 or OSPFv3 routing domain to
> >    know the capabilities of their neighbors and other routers in the
> >    routing domain.  This document proposes extensions to OSPFv2 and
> >    OSPFv3 for advertising optional router capabilities.  The Router
> >    Information (RI) Link State Advertisement (LSA) is defined for
this
> >    purpose.  In OSPFv2, the RI LSA will be implemented with an
opaque
> >    LSA type ID.  In OSPFv3, the RI LSA will be implemented with a
> unique
> >    LSA type function code.  In both protocols, the RI LSA can be
> >    advertised at any of the defined flooding scopes (link, area, or
> >    autonomous system (AS)).  This document obsoletes RFC 4970 by
> >    providing a revised specification including support for
> advertisement
> >    of multiple instances of the RI LSA and a TLV for functional
> >    capabilities.
> >
> >
> >
> >
> > The file can be obtained via
> > https://datatracker.ietf.org/doc/draft-ietf-ospf-rfc4970bis/
> >
> > IESG discussion can be tracked via
> > https://datatracker.ietf.org/doc/draft-ietf-ospf-rfc4970bis/ballot/
> >
> >
> > No IPR declarations have been submitted directly on this I-D.
> >
> >
> > _______________________________________________
> > OSPF mailing list
> > OSPF@ietf.org
> > https://www.ietf.org/mailman/listinfo/ospf
>