[OSPF] Signaling Entropy Label Capability Using OSPF - draft-ietf-ospf-mpls-elc-00

"Acee Lindem (acee)" <acee@cisco.com> Mon, 11 April 2016 17:38 UTC

Return-Path: <acee@cisco.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F20712F27A; Mon, 11 Apr 2016 10:38:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.517
X-Spam-Level:
X-Spam-Status: No, score=-15.517 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, 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 SU3s4l8RPdKd; Mon, 11 Apr 2016 10:38:42 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 750FD12F253; Mon, 11 Apr 2016 10:38:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=666; q=dns/txt; s=iport; t=1460396322; x=1461605922; h=from:to:cc:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=yc2GuvDinpc7HDdHPS/oyyh5ywvjJNBCWi69NKtIaJw=; b=jb+mwpVpo0Ks6bSk0tpoBrH5rzS2/JcLlmJPLXvpMteyYaJ+guc0bduF qiUmr4tJsiJ7NTJ/fJLJHLHNXg16bHCDRiyn9efUQKToVMpzqvrqAjxHQ fYpP9OT5NJgvReFff+4+e8vQp8IdvA768DYn403Flw3NkiWAPcKiLO0xz M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ABAgCS4AtX/4oNJK1cgzeBVrhJgg8BD?= =?us-ascii?q?YFyhg0egRE4FAEBAQEBAQFlHAuERAQjEUUSASICJgIEMBUSBA6ILK1AkhMBAQE?= =?us-ascii?q?BAQEBAwEBAQEBARp8kS+CVgWYBAGOC4FRjTyPJQEeAQFCg2eKGX4BAQE?=
X-IronPort-AV: E=Sophos;i="5.24,462,1454976000"; d="scan'208";a="258554465"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 11 Apr 2016 17:38:41 +0000
Received: from XCH-RTP-015.cisco.com (xch-rtp-015.cisco.com [64.101.220.155]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id u3BHcfuu019569 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 11 Apr 2016 17:38:41 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-015.cisco.com (64.101.220.155) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Mon, 11 Apr 2016 13:38:41 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1104.009; Mon, 11 Apr 2016 13:38:41 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: "draft-ietf-ospf-mpls-elc@ietf.org" <draft-ietf-ospf-mpls-elc@ietf.org>
Thread-Topic: Signaling Entropy Label Capability Using OSPF - draft-ietf-ospf-mpls-elc-00
Thread-Index: AQHRlBj81Lqya0qQckSeteuSX15/fA==
Date: Mon, 11 Apr 2016 17:38:41 +0000
Message-ID: <D331595E.5903B%acee@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.116.152.202]
Content-Type: text/plain; charset="utf-8"
Content-ID: <D35F062462756C4CBAD0D0B1C8A4DC1F@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ospf/T_x5p4VI1iRPpU2KiwZZU_LoBC8>
Cc: OSPF WG List <ospf@ietf.org>
Subject: [OSPF] Signaling Entropy Label Capability Using OSPF - draft-ietf-ospf-mpls-elc-00
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.17
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: Mon, 11 Apr 2016 17:38:43 -0000

Authors, 

We will soon be progressing the OSPFv2 SR draft. What is your intent for
this draft? It is missing:
   
    1. A figure with the RI encoding like other OSPF documents
    2. Discussion as to precisely how the capability would be used by a
router in an OSPF routing domain. For example, must a router remove the EL
if the next-hop doesn’t support it?
    3. A discussion of backward compatibility for the new
Router-Information LSA capability.

Thanks,
Acee