IETF Logo Mail Archive

Re: [Isis-wg] I-D Action:draft-ietf-isis-layer2-05.txt

Ralph Droms <rdroms.ietf@gmail.com> Wed, 05 May 2010 12:36 UTC

Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: isis-wg@core3.amsl.com
Delivered-To: isis-wg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5A00A3A6B66 for <isis-wg@core3.amsl.com>; Wed, 5 May 2010 05:36:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.427
X-Spam-Level:
X-Spam-Status: No, score=-2.427 tagged_above=-999 required=5 tests=[AWL=0.172, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p-LLcShD6Sjd for <isis-wg@core3.amsl.com>; Wed, 5 May 2010 05:36:45 -0700 (PDT)
Received: from mail-qy0-f191.google.com (mail-qy0-f191.google.com [209.85.221.191]) by core3.amsl.com (Postfix) with ESMTP id EBC7F3A6B94 for <isis-wg@ietf.org>; Wed, 5 May 2010 05:36:40 -0700 (PDT)
Received: by qyk29 with SMTP id 29so7447741qyk.14 for <isis-wg@ietf.org>; Wed, 05 May 2010 05:36:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:mime-version :subject:date:references:x-mailer; bh=Xu5vxV5NI5EGQoB1bt9ayC7qHf3QA+mQ3JL7bzQTnsc=; b=VyIbyv8HQJBnCZqWKlVA13iddgblWjVF/r1fzbp7w8oUZ5YRRNKEVS0x4DInWJsQW8 l2PZUVRDTS7VFlVrrhb7/gbWtEkvKBxZyJ8lUiMO9StB/dXNUMC7mi1+qrBIov2J9ZLL dGsBR5v3dFqTZ/Fg0E9TlGYFLk/IhD5nPsido=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:references :x-mailer; b=mExgGZtieGIJ8Cv+/fPaeFkkIA6ZzRCrYE4u1goiftO3qpay8taFMy2FiBqsg54LlD OpXVgCR1gTjVu3lz5e9Dc8cIGBy9dBmky7Elc/ctPaYwrI4bumRHQZCAQF3ecLGdaZP/ jYDEBoYP44SBjk25krX7xlZltrZuXi/R+Rysc=
Received: by 10.224.17.196 with SMTP id t4mr5500488qaa.254.1273062981918; Wed, 05 May 2010 05:36:21 -0700 (PDT)
Received: from bxb-rdroms-8711.cisco.com (198-135-0-233.cisco.com [198.135.0.233]) by mx.google.com with ESMTPS id bv23sm2044166qcb.1.2010.05.05.05.36.20 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 05 May 2010 05:36:21 -0700 (PDT)
Message-Id: <2C0EBEE1-40FA-43E8-B1D0-760801939063@gmail.com>
From: Ralph Droms <rdroms.ietf@gmail.com>
To: isis-wg@ietf.org
In-Reply-To: <5E893DB832F57341992548CDBB33316398387204F7@EMBX01-HQ.jnpr.net>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Wed, 05 May 2010 08:36:19 -0400
References: <2FEA927D4859134F939C41B656EBB21C0AE06EB0@xmb-sjc-21e.amer.cisco.com> <2FEA927D4859134F939C41B656EBB21C0AE06EB6@xmb-sjc-21e.amer.cisco.com> <60C093A41B5E45409A19D42CF7786DFD4F9AAE46AB@EUSAACMS0703.eamcs.ericsson.se> <E4F23FAE-2071-4B1E-AA4F-AD097FB683FF@gmail.com> <5E893DB832F57341992548CDBB33316398387204F7@EMBX01-HQ.jnpr.net>
X-Mailer: Apple Mail (2.936)
Subject: Re: [Isis-wg] I-D Action:draft-ietf-isis-layer2-05.txt
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isis-wg>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 May 2010 12:36:46 -0000

John - I understand that OTV is a proprietary protocol.  My questino  
was asked to find out about applicability of those PDUs - which  
protocols require which PDUs, and what is the motivation for including  
each of those PDUs in draft-ietf-isis-layer2-05.txt.

- Ralph

On May 5, 2010, at 8:21 AM 5/5/10, John E Drake wrote:

> Ralph,
>
> I think the point is that unlike TRILL, and IEEE 802.1aq, OTV is  
> proprietary - nobody other than its designers has any idea how it  
> works.
>
> Publishing a few of its TLVs does absolutely nothing regarding  
> interoperability.
>
> Thanks,
>
> John
>
>> -----Original Message-----
>> From: isis-wg-bounces@ietf.org [mailto:isis-wg-bounces@ietf.org] On  
>> Behalf
>> Of Ralph Droms
>> Sent: Wednesday, May 05, 2010 5:07 AM
>> To: isis-wg@ietf.org
>> Subject: Re: [Isis-wg] I-D Action:draft-ietf-isis-layer2-05.txt
>>
>> Which of TRILL, IEEE 802.1ag and OTV use each of the PDUs defined in
>> draft-ietf-isis-layer2-05.txt?  Is it possible to devise an
>> applicability or usage table, similar to the table for TLVs in  
>> section
>> 5, for the new PDUs?
>>
>> - Ralph
>>
>> _______________________________________________
>> Isis-wg mailing list
>> Isis-wg@ietf.org
>> https://www.ietf.org/mailman/listinfo/isis-wg

v2.23.0 | Report a Bug | By Email