[L1vpn] Re: [OSPF] Fw: Four L1VPN working group last calls
Anton Smirnov <asmirnov@cisco.com> Thu, 11 October 2007 17:05 UTC
Return-path: <l1vpn-bounces@lists.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ig1TC-00042j-MS; Thu, 11 Oct 2007 13:05:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ifzly-0006yb-9B; Thu, 11 Oct 2007 11:16:26 -0400
Received: from no-more.cisco.com ([64.104.206.251] helo=av-tac-apt.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ifzlr-0006E9-63; Thu, 11 Oct 2007 11:16:26 -0400
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost [127.0.0.1]) by av-tac-apt.cisco.com (8.11.7p3+Sun/8.11.7) with ESMTP id l9BFGAj13519; Fri, 12 Oct 2007 01:16:10 +1000 (EST)
Received: from [128.107.163.254] (dhcp-128-107-163-254.cisco.com [128.107.163.254]) by strange-brew.cisco.com (8.11.7p3+Sun/8.11.7) with ESMTP id l9BFG6I20532; Thu, 11 Oct 2007 17:16:07 +0200 (CEST)
Message-ID: <470E3E35.7060400@cisco.com>
Date: Thu, 11 Oct 2007 08:16:05 -0700
From: Anton Smirnov <asmirnov@cisco.com>
Organization: Cisco Systems, Inc.
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Adrian Farrel <adrian@olddog.co.uk>
References: <02e801c8013c$9df58d00$0200a8c0@your029b8cecfe>
In-Reply-To: <02e801c8013c$9df58d00$0200a8c0@your029b8cecfe>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
X-Mailman-Approved-At: Thu, 11 Oct 2007 13:05:08 -0400
Cc: ospf@ietf.org, l1vpn@ietf.org
Subject: [L1vpn] Re: [OSPF] Fw: Four L1VPN working group last calls
X-BeenThere: l1vpn@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer 1 Virtual Private Networks <l1vpn.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>, <mailto:l1vpn-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@lists.ietf.org>
List-Help: <mailto:l1vpn-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>, <mailto:l1vpn-request@lists.ietf.org?subject=subscribe>
Errors-To: l1vpn-bounces@lists.ietf.org
Hi Adrian, all, I know it is damn close to last call deadline but I wanted to question format of data propagated via OSPF in http://www.ietf.org/internet-drafts/draft-ietf-l1vpn-ospf-auto-discovery-03.txt Format of TLVs propagated via L1VPN LSA proposed as: ----- 3.2. L1VPN INFO TLV The following TLV is introduced: Name: L1VPN IPv4 Info Type: 1 Length: Variable 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | L1VPN TLV length | L1VPN TLV Type | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ... TLV length The length of the TLV in bytes, including the 4 bytes of the TLV header. ----- So here length comes before TLV type (so strictly speaking it should be called LTV throughout the document) and length includes TLV header. Just about every TLV so far standardized to be propagated via OSPF has Type field coming first and length covering only value field (see TLV definitions in TE, GR, RCAP, LLS, tags and whatsnot). Wouldn't it be prudent to avoid divergence and make implementator's life slightly easier to follow the suit? OSPF is used here merely as a transport protocol for L1VPN discovery values so it is better if definition of service fields is more friendly toward existing OSPF practices. Thanks, Anton Adrian Farrel wrote: > Hi OSPF working group, > > The L1VPN working group is holding a last call on several drafts. One of > them uses OSPF to advertise L1VPN membership. > > This I-D has previously been presented to the OSPF working group and > some feedback has been incorporated. We would welcome any further > thoughts during the last call. By preference, please send comments to > the L1VPN list, but anything sent to the OSPF list will be forwarded. > > Thanks, > Adrian > ----- Original Message ----- From: "Adrian Farrel" <adrian@olddog.co.uk> > To: <l1vpn@ietf.org> > Sent: Thursday, September 27, 2007 8:17 PM > Subject: [L1vpn] Four working group last calls > > >> Hi, >> >> Now that there is a bit of peace and quiet on the CCAMP last calls, we >> would like to hold L1VPN last calls on four I-Ds: >> >> http://www.ietf.org/internet-drafts/draft-ietf-l1vpn-applicability-basic-mode-02.txt >> >> http://www.ietf.org/internet-drafts/draft-ietf-l1vpn-basic-mode-02.txt >> http://www.ietf.org/internet-drafts/draft-ietf-l1vpn-bgp-auto-discovery-02.txt >> >> http://www.ietf.org/internet-drafts/draft-ietf-l1vpn-ospf-auto-discovery-03.txt >> >> >> Since there are four drafts, we will make this a three week last call. >> It will complete at 12 noon GMT on 18th October 2007. >> >> We will be notifying the IDR, OSPF, and CCAMP working groups about >> this last call. >> >> Thanks, >> Adrian, Hamid, and Tomonori > > > > _______________________________________________ > OSPF mailing list > OSPF@ietf.org > https://www1.ietf.org/mailman/listinfo/ospf _______________________________________________ L1vpn mailing list L1vpn@lists.ietf.org https://www1.ietf.org/mailman/listinfo/l1vpn
- [L1vpn] Re: [OSPF] Fw: Four L1VPN working group l… Lou Berger
- [L1vpn] Re: [OSPF] Fw: Four L1VPN working group l… Adrian Farrel
- [L1vpn] Re: [OSPF] Fw: Four L1VPN working group l… Anton Smirnov