Re: [Isis-wg] Request for WG adoption of draft-xu-isis-mpls-elc-00

"Bragg, Nigel" <> Thu, 05 June 2014 15:43 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 39DB91A025C for <>; Thu, 5 Jun 2014 08:43:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.267
X-Spam-Status: No, score=-2.267 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id e6JkUB1cqKZw for <>; Thu, 5 Jun 2014 08:43:21 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0E7091A00C6 for <>; Thu, 5 Jun 2014 08:42:53 -0700 (PDT)
Received: from pps.filterd ( []) by (8.14.5/8.14.5) with SMTP id s55FeHK6025888; Thu, 5 Jun 2014 11:42:47 -0400
Received: from ( []) by with ESMTP id 1mau9182c3-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 05 Jun 2014 11:42:46 -0400
Received: from ( by ( with Microsoft SMTP Server (TLS) id; Thu, 5 Jun 2014 11:42:43 -0400
Received: from ([]) by ([::1]) with mapi; Thu, 5 Jun 2014 11:42:42 -0400
From: "Bragg, Nigel" <>
To: Robert Raszuk <>
Date: Thu, 5 Jun 2014 11:42:39 -0400
Thread-Topic: [Isis-wg] Request for WG adoption of draft-xu-isis-mpls-elc-00
Thread-Index: Ac+AzYn+J7dOXIx9STyDM3VuCXH91AAA52lw
Message-ID: <>
References: <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-Product-Ver: SMEX-
X-TM-AS-Result: No--10.852100-8.000000-31
X-TM-AS-User-Approved-Sender: No
X-TM-AS-User-Blocked-Sender: No
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.12.52, 1.0.14, 0.0.0000 definitions=2014-06-05_05:2014-06-05,2014-06-05,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1406050189
Cc: "" <>, "" <>, "" <>
Subject: Re: [Isis-wg] Request for WG adoption of draft-xu-isis-mpls-elc-00
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF IS-IS working group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 05 Jun 2014 15:43:28 -0000

I agree with you, Robert, for fundamental reasons.   When you stand back there are two ways of mitigating network congestion :
-	spread the offered load over the widest range of routes available,  or
-	place load onto routes specifically selected to minimize the chance of conflict for resources.
ECMP mechanizes one of these, SR the other;  they are bookends.

So, launch with entropy immediately under the top (i.e.  egress node) label -- goes ECMP route;
Anything else is parsed as an SR label stack ?
-	far too simple  :-), but might be a start.

-----Original Message-----
From: Isis-wg [] On Behalf Of Robert Raszuk
Sent: 05 June 2014 15:50
To: Nobo Akiya (nobo)
Subject: Re: [Isis-wg] Request for WG adoption of draft-xu-isis-mpls-elc-00

> always advertise _max_ number of SIDs for ECMP.

I meant that. No point to go lower at all.

> Still, in an SR network consisting of 100 nodes ... each network node used to have 100 node SID forwarding entries (assuming one SID advertised per node) but now each network node will have 3200 or 6400 or 12800 node SID forwarding entries. That's a huge increase.

Assume no aggregation it looks huge, but it's tiny if you compare it with state required on ingress as example where all of your overlay services reside.

> Sure the forwarding table can do some aggregation but number of "resources" reserved, consumed, advertised and OAM requires to support them are still enlarged significantly.

I do not agree. Assume v6 SR where I advertise instead of single SID say a block of /96. It is still one prefix for all what forwarding needs to care about.  What would be different for that prefix vs /128 prefix from the point of view of  "resources" reserved, consumed, advertised and OAM ?

> I still see tackling EL to be appealing :)

Is this still more appealing then say mpls over UDP draft ;-) ?


Isis-wg mailing list