Re: WGLC for draft-ietf-rtgwg-cl-use-cases

Curtis Villamizar <curtis@ipv6.occnc.com> Fri, 14 February 2014 22:53 UTC

Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0FC61A029A for <rtgwg@ietfa.amsl.com>; Fri, 14 Feb 2014 14:53:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level:
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uftDcxy8wbvE for <rtgwg@ietfa.amsl.com>; Fri, 14 Feb 2014 14:53:45 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id 17D131A0251 for <rtgwg@ietf.org>; Fri, 14 Feb 2014 14:53:44 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s1EMrbpK024138; Fri, 14 Feb 2014 17:53:37 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201402142253.s1EMrbpK024138@maildrop2.v6ds.occnc.com>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: WGLC for draft-ietf-rtgwg-cl-use-cases
In-reply-to: Your message of "Fri, 14 Feb 2014 16:14:26 +0000." <CF23AB10.4BD19%aretana@cisco.com>
Date: Fri, 14 Feb 2014 17:53:37 -0500
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/daqwM4VfYii2gSs9-oe_mq4Y3nU
Cc: "draft-ietf-rtgwg-cl-use-cases@tools.ietf.org" <draft-ietf-rtgwg-cl-use-cases@tools.ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Feb 2014 22:53:49 -0000

Support - as co-author

This document has information in a few areas that for clarity we would
have to put in other documents if it were not here:

  1.  The two fundamental use cases - parallel simple links and
      parallel paths (plus links).

  2.  Some uses of the advanced features -

      a.  delay sesitive applications,
      b.  accounting for IP and LDP traffic
      c.  packet ordering considerations

  3.  Common practice today.  (the appendices)

Rather than put some of this in a few other documents and clutter them
it is better to have a purely informational document that we can
reference.

Without the background information on common practice we have to refer
to some older documents like RFC299{1,2} and the PW avoiding ECMP RFC
[RFC4928] that are inadequate for that background information.

Curtis


In message <CF23AB10.4BD19%aretana@cisco.com>
"Alvaro Retana (aretana)" writes:
> 
> Hi!
>  
> This message starts the Working Group Last Call for
> draft-ietf-rtgwg-cl-use-cases.  This call will close by EOD (pick your
> favorite time zone) on February 28, 2014.
>  
> http://tools.ietf.org/html/draft-ietf-rtgwg-cl-use-cases
>  
> Please provide specific feedback as to why you support (or not) the
> advancement of this draft.  Please about "+1"-type responses.
>  
> Thanks!
>  
> Alvaro.