[fun] Fwd: New Version Notification for draft-baker-fun-routing-class-00.txt
Fred Baker <fred@cisco.com> Sat, 02 July 2011 06:20 UTC
Return-Path: <fred@cisco.com>
X-Original-To: fun@ietfa.amsl.com
Delivered-To: fun@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 366C511E80E3 for <fun@ietfa.amsl.com>; Fri, 1 Jul 2011 23:20:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.47
X-Spam-Level:
X-Spam-Status: No, score=-110.47 tagged_above=-999 required=5 tests=[AWL=0.129, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 j-cfWz0PEH1k for <fun@ietfa.amsl.com>; Fri, 1 Jul 2011 23:20:16 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by ietfa.amsl.com (Postfix) with ESMTP id 934CF11E80B2 for <fun@ietf.org>; Fri, 1 Jul 2011 23:20:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=1316; q=dns/txt; s=iport; t=1309587615; x=1310797215; h=from:subject:date:references:to:message-id:mime-version: content-transfer-encoding; bh=4CTLTKPtS0htDNUOdDU1BdD8VlFc5duTxJwe97DMnr0=; b=ep6m4xoBBJiaO8iV/ZZyB3rdY9dso3AwENOgZkkCuZLrZDs+XbeZVg+m Z4778eelOSOuc5/P3exG/AjwezHy/+8OsoQPx7w5LIFPoYqcMyxRpb2PP mBZ6SOEI/jVKenCwBBYMHQObzxONowTnlckicnYSOv45xSNZqROVTCkoL s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ap0IAFW3Dk6rRDoH/2dsb2JhbABSmQ+Oc3eIeqVTnUSGNQSHP4p1hHiLXQ
X-IronPort-AV: E=Sophos;i="4.65,462,1304294400"; d="scan'208";a="473850845"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by sj-iport-1.cisco.com with ESMTP; 02 Jul 2011 06:20:15 +0000
Received: from Freds-Computer.local (sjc-vpn2-1521.cisco.com [10.21.117.241]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p626KFgq024069 for <fun@ietf.org>; Sat, 2 Jul 2011 06:20:15 GMT
Received: from [127.0.0.1] by Freds-Computer.local (PGP Universal service); Fri, 01 Jul 2011 23:20:15 -0700
X-PGP-Universal: processed; by Freds-Computer.local on Fri, 01 Jul 2011 23:20:15 -0700
From: Fred Baker <fred@cisco.com>
Date: Fri, 01 Jul 2011 23:20:07 -0700
References: <20110702061725.26914.78761.idtracker@ietfa.amsl.com>
To: fun@ietf.org
Message-Id: <F84AF470-C67F-4EE7-8FA5-59F624BAE5F3@cisco.com>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: [fun] Fwd: New Version Notification for draft-baker-fun-routing-class-00.txt
X-BeenThere: fun@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "FUture home Networking \(FUN\)" <fun.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/fun>, <mailto:fun-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/fun>
List-Post: <mailto:fun@ietf.org>
List-Help: <mailto:fun-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/fun>, <mailto:fun-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Jul 2011 06:20:17 -0000
FYI Begin forwarded message: > From: internet-drafts@ietf.org > Date: July 1, 2011 11:17:25 PM PDT > To: fred@cisco.com > Cc: fred@cisco.com > Subject: New Version Notification for draft-baker-fun-routing-class-00.txt > > A new version of I-D, draft-baker-fun-routing-class-00.txt has been successfully submitted by Fred Baker and posted to the IETF repository. > > Filename: draft-baker-fun-routing-class > Revision: 00 > Title: Routing a Traffic Class > Creation date: 2011-07-01 > WG ID: Individual Submission > Number of pages: 14 > > Abstract: > This note addresses the concept of routing a traffic class. This has > many possible implementations, IGP and BGP, and link state as well as > distance vector. The fundamental impetus is the question raised in > RFC 3704 and shim6 of exit routing, the question raised by Mike > O'Dell of source/destination routing, and the "fish" problem, raised > in many networks, in which distinct traffic classes that could > conceivably use the same route predictably use different routes. > Instead of handling these as "destination routing with a twist", the > paper looks at the matter systemically. > > Requirements > > > > The IETF Secretariat