[Teas] Re: [mpls] Re: Call for adoption: draft-beeram-mpls-rsvp-sr-01 (Ends 2026-11-17)
Robert Raszuk <robert@raszuk.net> Wed, 18 November 2026 16:50 UTC
Received: from mail-qt1-x834.google.com (mail-qt1-x834.google.com [IPv6:2607:f8b0:4864:20::834]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mx.ietf.org (Postfix) with ESMTPS id A00444B for <teas@ietf.org>; Wed, 18 Nov 2026 16:50:22 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=raszuk.net header.s=google header.b=SmynwO+b; spf=pass (mx.ietf.org: domain of robert@raszuk.net designates 2607:f8b0:4864:20::834 as permitted sender) smtp.mailfrom=robert@raszuk.net; dmarc=none; arc=pass ("google.com:s=arc-20260327:i=1")
Received: by mail-qt1-x834.google.com with SMTP id d75a77b69052e-55b8cd4e2abso12103061cf.1 for <teas@ietf.org>; Wed, 18 Nov 2026 08:50:22 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; t=1795020622; cv=none; d=google.com; s=arc-20260327; b=C+vOnrvi5pvtuEp02FtCjlOYCcmVoHTa7y7CF+EmfesDO4yzhYkRULpH5Tqoy6c7cA 2LNTW/zYh5WTVIc8u+qDKEe4Uhf4NfMHHx21d9asorC9h1FiF8vQf7Vu/oClIylYm4lg /RD3z9AMft3h+hf2QLss60dFE0BTWwLyL7b+0t/CHOaOGxC6/SlnA9kO55CEOJRndmob KmZEBbZAA6eqHfnaCpDEAZh+6kXSRPo7+3Lsz5CF+T9SgTgtx20vGVEfJ+owfcL+QbZC 8VScp8QzqrRniECTIycBDuththo3yc4WsafiPnqB3x235i6/7mu43dONvoxEAZknHKF1 SdEA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20260327; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:dkim-signature; bh=2jpGOE9yhVPFKOPkodILaaZC/nswsIxGIZuCaiBYb94=; fh=uliJ9723xmA11LNermZ+PiWiVazFdfNHK5oyUomecBE=; b=HuD16rcU28+SZNL5xEUhiUvuBytWiMcCLXo/J0j2f8A2TGnWjbGRTludVC9pASMK3F vNE46gDWY6Yw00n2F+dfw6RU9sNEeWlxIHRuOlWJGyYcYB48G5TL86lt7wy+nepUha8W pD80K/Mrh65rSykjIPgE7FscThM/oDzIUnO00OLnASMU9m0B0ZYTZHwA6TqN3vDbjp8N 4JqI55S5cqWda3EXF5q7WQRh9PKZnUpQDIcnsvn3F7lWpiorFaBX+DK/QHxmeoydQxEa UHNFGlldZ68ZAdxWvHXemfMEQa61XUkOlXIc6YUVtaTkeN4B8SE2BS9v/2QagIPtv2bt 6Heg==; darn=ietf.org
ARC-Authentication-Results: i=1; mx.google.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; t=1795020622; x=1795625422; darn=ietf.org; h=content-type:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:from:to:cc:subject:date:message-id:reply-to :content-type; bh=2jpGOE9yhVPFKOPkodILaaZC/nswsIxGIZuCaiBYb94=; b=SmynwO+b0emCLIQqcxdg4vxdDuTzvdWvLyLMQXjp6PuMjF4B0WMVvI8/t3CS3RMEd4 BLg2Q3V7RZ/YyDsswo6PqVcEs8Q8bHusfbu8jfaqqgpV+pqlctPnbWxVazQboxfrAyfJ un9uxd3xVNqCyDtQoFKUBIzKYuxETVjFdk85UHhKD0/R6RcUvfEJhgGlTza0gwhtGZxF 4lWFS5IbJuvDdcLnFNgcQ0AxPxNEPIbyqvaxs0wzbuljqtxLXdvZ7DHmOVZPI6xUdLwK 97IC6HcpSLU5fuLIVdPe//edWZEiFh3DnmjmNJ7vTYD1YI0Lfl2R8oEkNj0q7kCXQ7zz w3hA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1795020622; x=1795625422; h=content-type:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:x-gm-gg:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to:content-type; bh=2jpGOE9yhVPFKOPkodILaaZC/nswsIxGIZuCaiBYb94=; b=xTn/ZsBFyjYdkm1uxQnVBR0E6FiQpkZjtU10nrTUvLx7E4FAgjlzy8hCVGxstOH0kL MiAsU6AjYOZ5SIqkX9znjC5QptJqbfQYZ7a6NKhJqjrDiy6xSLYS8A15FdnQc/0RzAxo Z/gIQOxrsZDgSUpasspxhjWX8nsrd6fP7QCzu7qxk1/BgZz7jBqRv+9JZX2EOW1V0aCU 8c2Snv45xcws0J7cnksiKl+YdxraVwuXGzYu+YEjI/YuvzmL+jernRGHAnFtTHVUShrE Jgyle3NSJwfvSPo6U2eASt7ygNJ3i/x4gHIJ6FFbeq2/d+0BvO8df+5EXICM80PHnb6y yFdQ==
X-Forwarded-Encrypted: i=1; AL+hErEP3nsrKWtUNSV432RWZxKquDfKOsKl5wOaUkm5AwI+dIXxS/0zsyn5bPd+FnwOFmLmQUsY@ietf.org
X-Gm-Message-State: APuU4Z8y/bifth+3SIiIhJtUDpkRF/G0OHLF5qmEEF+OIFIwFWvuVkAA nJJQDczlsmxD/jZlWpVlevU+4Ht2RbVObMFx0R9RagJ8uzgfKoBZ953Y3hmuX/mTm7NqVSgS1dq lSA5xk/ug+CqIueQ0PAwMz2/As7VLs5VZht0sYXf2bQ==
X-Gm-Gg: AYBFou2yTakhiqMWAqNbUqX16juYvjapQE+wCDPCCurKa4mSboI3g2joMWyOvqIhZz4 3UfrTyRfaf3W8C21PEed/a5GkKQR3cAyDhB7QkFJ8IyC+jtTZTqR702igG8vF71FjKrrLOZpDM2 Eb62gq9ioDrTpTAHrbJ3cUBa6oLhuMdtDZmTTXt9H11W7dgRuzLmT0OqvrkgXajmRtilfvD2OXV nvYiouU68CzJhfHBFdQyxiv0UL1QAyKITsEpCuOWlo+g+6bqV6RQxL2+5Fk0m4vQMOa6AQ6Yfik GxVIsQ7hO08kqbT+WRj8614HLPL5wZZ6a05I0/pQJgDRCSd8ngqtMd2hdXwCyDnZ1fEWyj51p0i GRl8BWFWaTY9h0aJfX5X44dqv5zKUyiRpBG9G
X-Received: by 2002:a05:622a:1b9e:b0:535:1f73:8d9e with SMTP id d75a77b69052e-55d5a5569e5mr49905181cf.17.1795020621753; Wed, 18 Nov 2026 08:50:21 -0800 (PST)
MIME-Version: 1.0
References: <179358330469.1013311.4077472205935423431@dt-datatracker-7dc874ff8f-sl5zv> <LV8P220MB1914664DC588F7968E9FFF31FC7A2@LV8P220MB1914.NAMP220.PROD.OUTLOOK.COM> <CA+b+ER=_WBfNGiJFXuRKqbTF4daFFhc+xKH-7L8RTKfwMoqt4A@mail.gmail.com> <SJ2PR84MB3370B21BB0826A9DE4C0071A927A2@SJ2PR84MB3370.NAMPRD84.PROD.OUTLOOK.COM>
In-Reply-To: <SJ2PR84MB3370B21BB0826A9DE4C0071A927A2@SJ2PR84MB3370.NAMPRD84.PROD.OUTLOOK.COM>
From: Robert Raszuk <robert@raszuk.net>
Date: Wed, 18 Nov 2026 17:50:10 +0100
X-Gm-Features: Aa3M54q1pw9jgT6rYbbGpBQo1JE731OUsJewEmTnIfbAjgoTlIjvTmiLVFdNvng
Message-ID: <CAOj+MME0Xxnsm4W-g0fiLnEGaw9n_+NxGMYBzhzAxPJHp479bw@mail.gmail.com>
To: "Barth, Colby" <jonathan.barth@hpe.com>
Content-Type: multipart/alternative; boundary="000000000000864ac306608fce80"
X-Spamd-Bar: ----------------
Message-ID-Hash: LZWL3SQKYK75LF6HEDQ456E56FY37TXT
X-Message-ID-Hash: LZWL3SQKYK75LF6HEDQ456E56FY37TXT
X-MailFrom: robert@raszuk.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-teas.ietf.org-0; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Robert Raszuk <rraszuk@gmail.com>, Tarek Saad <tsaad.net@gmail.com>, "mpls@ietf.org" <mpls@ietf.org>, "draft-beeram-mpls-rsvp-sr@ietf.org" <draft-beeram-mpls-rsvp-sr@ietf.org>, "TEAS WG (teas@ietf.org)" <teas@ietf.org>, spring <spring@ietf.org>, "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>, TEAS WG Chairs <teas-chairs@ietf.org>, spring Chairs <spring-chairs@ietf.org>
X-Mailman-Version: 3.3.10
Precedence: list
Subject: [Teas] Re: [mpls] Re: Call for adoption: draft-beeram-mpls-rsvp-sr-01 (Ends 2026-11-17)
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/PNZxqwLD_xPHui52O6fakez2s5g>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Owner: <mailto:teas-owner@ietf.org>
List-Post: <mailto:teas@ietf.org>
List-Subscribe: <mailto:teas-join@ietf.org>
List-Unsubscribe: <mailto:teas-leave@ietf.org>
Hi Colby, IMO we need to look at full picture before endorsing any new work which is based on legacy network architectures. Specifically we need to understand pros and cons (as Tarek started to enumerate) and make an educated judgement if proceeding with solution which in it's root is using BW accounting in the control plane a good and practical in 2026/2027 time frame. TE itself has proven to be very useful and lot's of networks are using various flavors of it. RSVP-TE is only a way to build orchestrated paths in the network. Clearly there are many other ways deployed today to accomplish the same. But I can't say the same about RSVP-TE style control plane BW reservations. While it is surely possible as listed below it has a number of issues and problems. I am glad you admit that those problems to co-exist in single network with non TE traffic or with in network replication like multicast are well-understood. But I have not seen a single RFC, BCP, Informational or even Experimental which would discuss how to handle them in a way that still makes your TE BW counters useful. See the difference is that if you consider all traffic to be equal class citizen then your BW accounting for fraction of the traffic in the network hardly makes a lot of sense. You need to deploy QoS to all traffic. Now we are facing a new challenge ... See in SR networks MLA and TI-LFA are widely used. Do you expect implementations to now consider your TE reservation counters when building bypasses or protection for non TE traffic ? And for protection this is still apparently an open topic. You seems to be indicating that solution for this (specifically link protection) would be RSVP-TE FRR at each hop. Would that still reuse IGP SIDs ? And one of the co-authors clearly indicated that node protection is out of scope. Let's consider this too, before dismissing the protection aspect. If any architecture does not work well (in 10s of ms) with node failures in the network should it be still endorsed by IETF these days ? Cheers, Robert On Wed, Nov 18, 2026 at 4:37 PM Barth, Colby <jonathan.barth= 40hpe.com@dmarc.ietf.org> wrote: > Hi Robert, > > I think we need to distinguish between general network engineering > challenges and issues specific to the solution proposed in this draft. > > The points you raise regarding non-TE traffic, multicast replication, > transient loops, and failure or congestion notification are not unique to > RSVP-TE. They apply, in varying degrees, to just about any network > architecture, including Segment Routing. > > Some specific observations: > > - > > RSVP-TE bandwidth reservations obviously do not require that 100% of > network traffic be carried in TE tunnels. Coexistence questions have > already been raised but importantly accounting for non-TE traffic and other > consumers of network resources is a well-understood engineering > consideration. It does not invalidate the benefits of distributed bandwidth > management and admission control. > - > > Multicast replication, transient forwarding loops, and microloops are > not RSVP-TE-specific problems. These are general networking challenges that > exist regardless of the TE technology being used. > - > > RSVP-TE has well-established mechanisms for failure detection, local > protection, and resource notification. In particular, RSVP-TE FRR provides > local protection without waiting for end-to-end signaling. Suggesting that > RSVP-TE relies on RESV_TEAR for fast failure recovery overlooks mechanisms > that have been widely deployed for decades. > > I take issue with the characterization of RSVP-TE as "legacy TE style > networking." RSVP-TE provides capabilities that remain valuable in modern > networks, particularly distributed bandwidth management, admission control, > and preemption. The fact that these mechanisms have been around for some > time doesn't make them obsolete. > > More importantly, I don't see how these concerns relate to the proposal in > this draft. The proposal is actually quite simple. It doesn't introduce a > new TE architecture or change how RSVP-TE bandwidth management works. It > simply allows existing RSVP-TE signaling and control-plane capabilities to > be used with an SR-MPLS forwarding plane. > > The relevant question for this adoption call is whether there is value in > applying RSVP-TE control-plane capabilities while also using SR-MPLS > forwarding. As a co-author, I obviously believe there is. > -- Colby > > > ------------------------------ > *From: *Robert Raszuk <rraszuk@gmail.com> > *Date: *Wednesday, November 18, 2026 at 3:52 AM > *To: *Tarek Saad <tsaad.net@gmail.com> > *Cc: *mpls@ietf.org <mpls@ietf.org>; draft-beeram-mpls-rsvp-sr@ietf.org < > draft-beeram-mpls-rsvp-sr@ietf.org>; TEAS WG (teas@ietf.org) < > teas@ietf.org>; spring <spring@ietf.org>; mpls-chairs@ietf.org < > mpls-chairs@ietf.org>; TEAS WG Chairs <teas-chairs@ietf.org>; spring > Chairs <spring-chairs@ietf.org> > *Subject: *Re: [mpls] Re: Call for adoption: draft-beeram-mpls-rsvp-sr-01 > (Ends 2026-11-17) > > Dear Tarek, > > Please kindly augment the section "Architectural Objections and Concerns > Key Opponents:" with some of concerns I raised: > > * Any TE BW allocation in the control plane work well when network > supports 100% of TE traffic. When there is no TE traffic in the network all > reservations made fall back to normal QoS - and there is not a good > universal mapping between queue depths and interface bandwidth > > * Any network which supports multicast or flexicast where there is in > network replication does not fit the end to end TE unicast model and > congestion is likely to occur. Note that traffic carried by those > technologies may be more important than unicast transit traffic. > > * Any loops and microloops formed in the network (even transient) may very > effectively jeopardize any end to end TE efforts. > > * RSVP-TE does not have any built in fast mechanisms to notify endpoints > about link failures (RSVP RESV_TEAR is too slow) or congestion nor can > notice any forms of brownouts. > > Yes those are high level observations not > introduced by draft-beeram-mpls-rsvp-sr alone, but IMO are important points > to consider when making judgement about progressing with more legacy TE > style of networking. > > Kind regards, > Robert > > > On Wed, Nov 18, 2026 at 7:02 AM Tarek Saad <tsaad.net@gmail.com> wrote: > > Thanks to everyone who participated in the adoption poll for > draft-beeram-mpls-rsvp-sr. I am including a summary of the discussion and a > proposal for the next steps below. > > Document: draft-beeram-mpls-rsvp-sr > Engagement: High (approx. 59 messages from 23 unique participants) > WGs Involved: MPLS, SPRING, TEAS > Current Version: -02 (posted 2026-11-15) > > > 1. Summary of Support from Key Proponents: > - Provides a practical, rational method for bandwidth reservation in > SR-MPLS networks. > - Leverages existing, mature RSVP-TE control planes while using the > SR-MPLS data plane (reusing Adj-SIDs). > - Provides distributed admission control without requiring a full > stateful PCE for all scenarios. > 2. Architectural Objections and Concerns Key Opponents: > - State Conflict: Contention that the draft introduces transit state > into SR, which critics argue violates RFC 8402 and RFC 8426 (stateless > transit nodes). > - Coexistence: Questions on how RSVP-TE signaled Adj-SIDs coexist > with IGP-distributed Adj-SIDs on the same forwarding plane. > - Value Proposition: Concerns that retrofitting RSVP-TE is a > tactical fix that may distract from long-term controller-based/PCE > solutions. > 3. Proposed Joint Interim Meeting (MPLS, SPRING, TEAS) Duration: 3 > Hours Objective: Resolve foundational architectural questions before > proceeding with adoption or determining WG homes. > > > To resolve the impasse, the MPLS chairs propose a joint interim meeting > between MPLS, SPRING, and TEAS (the date and time will be announced later). > > - Objective: Resolve foundational architectural questions before > proceeding with adoption or determining WG homes. > - Agenda Items: > - Scope: What are we trying to do? > - Reservation Locality: Where are the reservations made (transit, > ingress, or central)? > - Strict Hops: Does bandwidth reservation only make sense for > strict hops, regardless of reservation type (central or distributed)? > - Signaling Support: Is there broad support for a signaling plane > solution for distributed reservation? > - Protocol Evolution: Does it make sense to build on an existing > signaling protocol (like RSVP-TE)? > - Unified Solution: Should there be just one solution for both > MPLS-SR and SRv6? > - Architecture: What should the high-level solution look like? > > > > Regards, > Tarek (MPLS WG chair) > > *From: *Tarek Saad via Datatracker <noreply@ietf.org> > *Date: *Sunday, November 1, 2026 at 5:35 PM > *To: *mpls@ietf.org <mpls@ietf.org>; mpls-chairs@ietf.org < > mpls-chairs@ietf.org>; draft-beeram-mpls-rsvp-sr@ietf.org < > draft-beeram-mpls-rsvp-sr@ietf.org> > *Subject: *Call for adoption: draft-beeram-mpls-rsvp-sr-01 (Ends > 2026-11-17) > > This message starts a mpls WG Call for Adoption of: > draft-beeram-mpls-rsvp-sr-01 > > This Working Group Call for Adoption ends on 2026-11-17 > > Abstract: > RFC 8577 introduced the concept of signaling RSVP-TE tunnels on a > shared MPLS forwarding plane using preinstalled "TE link labels". > Those labels are functionally equivalent to Segment Routing (SR) > Adjacency Segment Identifiers (Adj-SIDs) but are allocated and > distributed solely via RSVP-TE signaling. > > This document extends RFC 8577 so that RSVP-TE tunnels can use > Segment Routing over MPLS (SR-MPLS) Adj-SIDs, as specified in RFC > 8402 and RFC 8660, in place of TE link labels. It restricts scope to > Adj-SIDs attached to a single unidirectional adjacency and defines > the signaling procedures and protocol extensions required to couple > the RSVP-TE control plane with the SR-MPLS data plane. > > Please reply to this message and indicate whether or not you support > adoption > of this Internet-Draft by the mpls WG. Comments to explain your preference > are greatly appreciated. Please reply to all recipients of this message and > include this message in your response. > > Authors, and WG participants in general, are reminded of the Intellectual > Property Rights (IPR) disclosure obligations described in BCP 79 [2]. > Appropriate IPR disclosures required for full conformance with the > provisions > of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any. > Sanctions available for application to violators of IETF IPR Policy can be > found at [3]. > > Thank you. > [1] https://datatracker.ietf.org/doc/bcp78/ > <https://urldefense.com/v3/__https://datatracker.ietf.org/doc/bcp78/__;!!NpxR!mC9SN0ss_tiv7hXAGw7R194fohBPEbeyKuN0NEa22sINUYwMXrptG2FM9p8-osqua02u7D56vTdf3Ie5$> > [2] https://datatracker.ietf.org/doc/bcp79/ > <https://urldefense.com/v3/__https://datatracker.ietf.org/doc/bcp79/__;!!NpxR!mC9SN0ss_tiv7hXAGw7R194fohBPEbeyKuN0NEa22sINUYwMXrptG2FM9p8-osqua02u7D56vX6AiIfc$> > [3] https://datatracker.ietf.org/doc/rfc6701/ > <https://urldefense.com/v3/__https://datatracker.ietf.org/doc/rfc6701/__;!!NpxR!mC9SN0ss_tiv7hXAGw7R194fohBPEbeyKuN0NEa22sINUYwMXrptG2FM9p8-osqua02u7D56vXTS7R9t$> > > The IETF datatracker status page for this Internet-Draft is: > https://datatracker.ietf.org/doc/draft-beeram-mpls-rsvp-sr/ > <https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-beeram-mpls-rsvp-sr/__;!!NpxR!mC9SN0ss_tiv7hXAGw7R194fohBPEbeyKuN0NEa22sINUYwMXrptG2FM9p8-osqua02u7D56vb7mTgr4$> > > There is also an HTMLized version available at: > https://datatracker.ietf.org/doc/html/draft-beeram-mpls-rsvp-sr-01 > <https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/draft-beeram-mpls-rsvp-sr-01__;!!NpxR!mC9SN0ss_tiv7hXAGw7R194fohBPEbeyKuN0NEa22sINUYwMXrptG2FM9p8-osqua02u7D56vTlnWSPC$> > > A diff from the previous version is available at: > https://author-tools.ietf.org/iddiff?url2=draft-beeram-mpls-rsvp-sr-01 > <https://urldefense.com/v3/__https://author-tools.ietf.org/iddiff?url2=draft-beeram-mpls-rsvp-sr-01__;!!NpxR!mC9SN0ss_tiv7hXAGw7R194fohBPEbeyKuN0NEa22sINUYwMXrptG2FM9p8-osqua02u7D56vXLK1TRv$> > _______________________________________________ > mpls mailing list -- mpls@ietf.org > To unsubscribe send an email to mpls-leave@ietf.org > > _______________________________________________ > Teas mailing list -- teas@ietf.org > To unsubscribe send an email to teas-leave@ietf.org >
- [Teas] Re: [spring] Call for adoption: draft-beer… Acee Lindem
- [Teas] Re: [spring] Call for adoption: draft-beer… Vishnu Pavan Beeram
- [Teas] Re: Call for adoption: draft-beeram-mpls-r… Andrew Stone (Nokia)
- [Teas] Re: [mpls] Re: Call for adoption: draft-be… Robert Raszuk
- [Teas] Re: Call for adoption: draft-beeram-mpls-r… Vishnu Pavan Beeram
- [Teas] Re: [mpls] Re: Call for adoption: draft-be… Robert Raszuk
- [Teas] Re: [mpls] Re: Call for adoption: draft-be… Vishnu Pavan Beeram
- [Teas] Re: [mpls] Re: Call for adoption: draft-be… Robert Raszuk
- [Teas] Re: [spring] Re: [mpls] Re: Call for adopt… Robert Raszuk
- [Teas] Re: [spring] Re: [mpls] Re: Call for adopt… Robert Raszuk
- [Teas] Re: [spring] Re: [mpls] Re: Call for adopt… Andrew Stone (Nokia)
- [Teas] Re: [spring] Re: [mpls] Re: Call for adopt… Robert Raszuk
- [Teas] Re: [spring] Re: [mpls] Re: Call for adopt… Vishnu Pavan Beeram
- [Teas] Re: [spring] Re: [mpls] Re: Call for adopt… Robert Raszuk
- [Teas] Re: [spring] Re: [mpls] Re: Call for adopt… Vishnu Pavan Beeram
- [Teas] Re: [spring] Re: [mpls] Re: Call for adopt… Vishnu Pavan Beeram
- [Teas] Re: [spring] Re: [mpls] Re: Call for adopt… Andrew Stone (Nokia)
- [Teas] Re: [spring] Re: [mpls] Re: Call for adopt… Vishnu Pavan Beeram
- [Teas] Re: [spring] Re: Call for adoption: draft-… Zafar Ali (zali)
- [Teas] Re: [spring] Re: Call for adoption: draft-… Vishnu Pavan Beeram
- [Teas] Re: [spring] Re: Call for adoption: draft-… Vishnu Pavan Beeram
- [Teas] Comments during Spring session - Re: [spri… Zafar Ali (zali)
- [Teas] Re: [spring] Comments during Spring sessio… Vishnu Pavan Beeram
- [Teas] Re: [mpls] Re: [spring] Comments during Sp… Robert Raszuk
- [Teas] Re: [mpls] Re: [spring] Comments during Sp… Vishnu Pavan Beeram
- [Teas] Re: [mpls] Re: [spring] Comments during Sp… Robert Raszuk
- [Teas] Re: [spring] Re: [mpls] Re: Comments durin… Robert Raszuk
- [Teas] Re: [mpls] Re: [spring] Comments during Sp… Vishnu Pavan Beeram
- [Teas] Re: [spring] Re: [mpls] Re: Comments durin… Robert Raszuk
- [Teas] Re: [spring] Re: [mpls] Re: Comments durin… Vishnu Pavan Beeram
- [Teas] Re: [spring] Re: Call for adoption: draft-… Zafar Ali (zali)
- [Teas] Re: Call for adoption: draft-beeram-mpls-r… Tarek Saad
- [Teas] Re: [mpls] Re: Call for adoption: draft-be… Robert Raszuk
- [Teas] Re: [mpls] Re: Call for adoption: draft-be… Barth, Colby
- [Teas] Re: [mpls] Re: Call for adoption: draft-be… Robert Raszuk
- [Teas] Re: [mpls] Re: Call for adoption: draft-be… Greg Mirsky
- [Teas] Re: [spring] Re: [mpls] Re: Call for adopt… Robert Raszuk