Re: [trill] Thoughts on active-active edge

"Tissa Senevirathne (tsenevir)" <tsenevir@cisco.com> Wed, 12 December 2012 23:14 UTC

Return-Path: <tsenevir@cisco.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B60AB21E8054 for <trill@ietfa.amsl.com>; Wed, 12 Dec 2012 15:14:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.017
X-Spam-Level:
X-Spam-Status: No, score=-9.017 tagged_above=-999 required=5 tests=[AWL=1.582, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id penpgwVxRtYW for <trill@ietfa.amsl.com>; Wed, 12 Dec 2012 15:14:20 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id D22C41F0CC5 for <trill@ietf.org>; Wed, 12 Dec 2012 15:14:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2781; q=dns/txt; s=iport; t=1355354058; x=1356563658; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=hzuiGoVIkL91VhSEITyoUIC2fmXTveqQa7PJopuZwpM=; b=WNCrLsFmFDvJ/rbTfYlab7dARpxoPmJ7fyi2TNvI50uh80khbNoEZ5Pe Kf3k2eeshctB45D9c8LGGDs1eaQqubfHbLBnCjifNgbfRO3OBGFpNrsv1 sANpM70pMKXeXhNJKaKbaKKK08Q+6zs3VysNz2i+fGZyccyWg6XPjL0TN 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAFIPyVCtJV2d/2dsb2JhbABFvnAWc4IeAQEBAwE6PwUHBAIBCBEEAQELFAkHIREUCQgCBAENBQgTh2QDCQa0LQ2JVYtiaYNiYQOUM40NhRGCc4Ii
X-IronPort-AV: E=Sophos;i="4.84,269,1355097600"; d="scan'208";a="152360441"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-3.cisco.com with ESMTP; 12 Dec 2012 23:14:18 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id qBCNEIsU010073 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 12 Dec 2012 23:14:18 GMT
Received: from xmb-rcd-x08.cisco.com ([169.254.8.240]) by xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.02.0318.004; Wed, 12 Dec 2012 17:14:17 -0600
From: "Tissa Senevirathne (tsenevir)" <tsenevir@cisco.com>
To: Thomas Narten <narten@us.ibm.com>, Sam Aldrin <aldrin.ietf@gmail.com>
Thread-Topic: [trill] Thoughts on active-active edge
Thread-Index: AQHN1+GJAcUGAj4DtkSKdF8jmxk4o5gUnyzwgABxZQD//5vnwIAAcUyAgADilACAAAI4AIAABGIAgAAmC4D//516wA==
Date: Wed, 12 Dec 2012 23:14:16 +0000
Message-ID: <FBEA3E19AA24F847BA3AE74E2FE19356288937A0@xmb-rcd-x08.cisco.com>
References: <CAFOuuo4zvX5AtD-oGRRftuZaKmhY7C7-SvDjznMOdzUj+Q3fGQ@mail.gmail.com> <FBEA3E19AA24F847BA3AE74E2FE1935628892DF6@xmb-rcd-x08.cisco.com> <CAFOuuo5LP1EzajpeBri2KhTT-wf+vv=JwmTLma9_mxg7dM5PvQ@mail.gmail.com> <FBEA3E19AA24F847BA3AE74E2FE1935628892EAE@xmb-rcd-x08.cisco.com> <4552F0907735844E9204A62BBDD325E732138B02@SZXEML507-MBS.china.huawei.com> <EE1367B6-5498-492E-A57A-155312162CFC@gmail.com> <201212122025.qBCKPmM7013618@cichlid.raleigh.ibm.com> <0E430FEE-F2AD-4EA0-9E98-50762B563E9B@gmail.com> <201212122257.qBCMvdeW014734@cichlid.raleigh.ibm.com>
In-Reply-To: <201212122257.qBCMvdeW014734@cichlid.raleigh.ibm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.155.1.164]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Mingui Zhang <zhangmingui@huawei.com>, Radia Perlman <radiaperlman@gmail.com>, "trill@ietf.org" <trill@ietf.org>
Subject: Re: [trill] Thoughts on active-active edge
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/trill>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Dec 2012 23:14:21 -0000

I think we should answer the question in hand first.

This thread is all about "saying it is ok to have MAC move in TRILL to solve active-active edge"

I am overwhelmingly against that statement and the argument for it is all based on whole series of assumptions and ignoring the modern networking devices and how they operate.

Once that is resolved and behind we can have a separate discussion of CMT, hu draft and future approach etc.

Thanks
Tissa

-----Original Message-----
From: Thomas Narten [mailto:narten@us.ibm.com] 
Sent: Wednesday, December 12, 2012 2:58 PM
To: Sam Aldrin
Cc: Mingui Zhang; Tissa Senevirathne (tsenevir); Radia Perlman; trill@ietf.org
Subject: Re: [trill] Thoughts on active-active edge


Sam Aldrin <aldrin.ietf@gmail.com> writes:

> On Dec 12, 2012, at 12:25 PM, Thomas Narten <narten@us.ibm.com> wrote:

> >> I believe we have discussed these scenarios (different solution
> >> types) previously.  WG should reach consensus and move forward with 
> >> the agreed solution.  Atleast from the IETF WG sessions, I presumed 
> >> there was a consensus on the solution.  Am I wrong in that 
> >> assumption?
> > 
> > what "solution" are you referring above as maybe having consensus?

> Cmt draft

If you mean draft-ietf-trill-cmt-01.txt, I at least am not in agreement.

I have several issues with the document.

For starters, it's incomplete. It needs to be paired with another document to get an actual "standard" you can implement. We don't have such a companion document yet.  It's been suggested that draft-hu-trill-pseudonode-nickname-04.txt is one such document. But that document is not a WG document and I'm not sure what its status is. (And it needs work...)

As a general rule (not TRILL specific) I don't like WGs doing "partial work" where they standardize one document, that is incomplete by itself, independent of other documents that are needed to produce a complete implementable solution to some real problem.

I've raised issues on the list about CMT and its unclarity wrt. LAG/MC-LAG, etc. I did not really get my questions answered.

What I'd really like to start with on CMT is a clear problem statement. I.e., exactly what problem/use case it is trying to solve. I have not been able to get that out of the two  documents.

As for draft-hu-trill-pseudonode-nickname-04.txt, I have other concerns. E.g., it talks about tunneling at one point, but that is completely unspecified.

What I don't want to do is spend a lot of time on the *solution* details. I first want a clear problem statement/use case. Without that, it is difficult to assess how well potential solutions address the stated problem.

Thomas