[CDNi] draft-ietf-cdni-use-cases to replace RFC3570 "Content Internetworking (CDI) Scenarios"
Francois Le Faucheur <flefauch@cisco.com> Fri, 01 June 2012 13:49 UTC
Return-Path: <flefauch@cisco.com>
X-Original-To: cdni@ietfa.amsl.com
Delivered-To: cdni@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B9EB11E8229 for <cdni@ietfa.amsl.com>; Fri, 1 Jun 2012 06:49:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.528
X-Spam-Level:
X-Spam-Status: No, score=-10.528 tagged_above=-999 required=5 tests=[AWL=0.071, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CzFGvJWodfys for <cdni@ietfa.amsl.com>; Fri, 1 Jun 2012 06:49:02 -0700 (PDT)
Received: from ams-iport-4.cisco.com (ams-iport-4.cisco.com [144.254.224.147]) by ietfa.amsl.com (Postfix) with ESMTP id 4DEE111E8215 for <cdni@ietf.org>; Fri, 1 Jun 2012 06:49:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=flefauch@cisco.com; l=856; q=dns/txt; s=iport; t=1338558542; x=1339768142; h=from:content-transfer-encoding:subject:date:message-id: to:mime-version; bh=fexc1So5jvTkBVnpgUUhAD9Dsf1ur6cXzZzmQ2AgHJU=; b=aKGf8n7aTLhUcOeNXZtXgo1aI0Myo75hYDyJn7Q6yfIaz2Xqe1rMVAvw Crqbq8WKKKhc3dzTM2eoYbiRkgSdWDe3Cdwka0SGXIX4DXb8rgaXT9Ysk XvZrU+jaIGLUprf9PZIoXMlwIkhTyhZnpAHQuywVtvb/FwWlR6ui8JzRz o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvwEAJLHyE+Q/khR/2dsb2JhbABFtDeBB4IxASeCModplwGBKJ95jW6CNmADlRmOD4FmgmI
X-IronPort-AV: E=Sophos;i="4.75,698,1330905600"; d="scan'208";a="5265779"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-4.cisco.com with ESMTP; 01 Jun 2012 13:49:01 +0000
Received: from ams-flefauch-8713.cisco.com (ams-flefauch-8713.cisco.com [10.55.161.196]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id q51Dn03D027146 for <cdni@ietf.org>; Fri, 1 Jun 2012 13:49:01 GMT
From: Francois Le Faucheur <flefauch@cisco.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 01 Jun 2012 15:49:00 +0200
Message-Id: <9FE94F85-3D0B-49A1-87EA-81BD21AA799A@cisco.com>
To: cdni@ietf.org
Mime-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
Subject: [CDNi] draft-ietf-cdni-use-cases to replace RFC3570 "Content Internetworking (CDI) Scenarios"
X-BeenThere: cdni@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "This list is to discuss issues associated with the Interconnection of Content Delivery Networks \(CDNs\)" <cdni.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cdni>, <mailto:cdni-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/cdni>
List-Post: <mailto:cdni@ietf.org>
List-Help: <mailto:cdni-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cdni>, <mailto:cdni-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jun 2012 13:49:03 -0000
Hello, Producing the Document Shepherd writeup for submission of draft-ietf-cdni-use-cases to IESG review raised the question of whether any existing RFCs would have their status changed by publication of this document. We discussed this among co-authors of CDNI documents, chairs and responsible AD, and concluded that draft-ietf-cdni-use-cases should replace RFC3570 "Content Internetworking (CDI) Scenarios". And similarly, we propose that cdni-framework should eventually replace RFC3466 "A Model for Content Internetworking (CDI)". This is essentially because these older RFCs touch on very similar scenarios but propose terminology and models that are slightly different to the more up-to-date ones proposed in our CDNI documents. Let us know if you have comments or concerns with that. Cheers Francois
- [CDNi] draft-ietf-cdni-use-cases to replace RFC35… Francois Le Faucheur