
From flefauch@cisco.com  Mon May  6 00:17:33 2013
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 5C63121F8E9A for <cdni@ietfa.amsl.com>; Mon,  6 May 2013 00:17:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.998
X-Spam-Level: 
X-Spam-Status: No, score=-9.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_63=0.6, 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 HmyL6H+5HCQg for <cdni@ietfa.amsl.com>; Mon,  6 May 2013 00:17:28 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 1DF9A21F8E98 for <cdni@ietf.org>; Mon,  6 May 2013 00:17:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=29579; q=dns/txt; s=iport; t=1367824648; x=1369034248; h=from:to:subject:date:message-id:mime-version; bh=rmDazHmyUHUb+11wBsac0SDcH6KlWlBUGaeGjGw+k2U=; b=U9RmgVcURdyKUvGjeSjelNDaL37bnT/aBtxBg4nfsiHuX9TWHcJ/OM+6 Majkfl41uaJ0qEMQcmdKzq1/FXmizD6h3rLavE/SD0ZBHBVHz4OoAjRKb W9B/EiqLn0r/vy1bfrXjyjv8ui9csQeldV9vgxCtpPA3EPP4xIcHgawLj Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmAFAKZYh1GtJXG9/2dsb2JhbAA2FwOCQ0Q3vwKBBhZtB4IhAQICZgIjARwOCgQIAQM8JAMBAxuIBAwzoEOSeItVjW8bdiABDBwHglphA6higjxRgXI1
X-IronPort-AV: E=Sophos;i="4.87,619,1363132800";  d="scan'208,217";a="206789938"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-5.cisco.com with ESMTP; 06 May 2013 07:17:27 +0000
Received: from xhc-rcd-x11.cisco.com (xhc-rcd-x11.cisco.com [173.37.183.85]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id r467HRgQ030873 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <cdni@ietf.org>; Mon, 6 May 2013 07:17:27 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.56]) by xhc-rcd-x11.cisco.com ([173.37.183.85]) with mapi id 14.02.0318.004; Mon, 6 May 2013 02:17:26 -0500
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "cdni@ietf.org" <cdni@ietf.org>
Thread-Topic: CDNI Logging - Series of Informal Meetings
Thread-Index: AQHOSinCyYxSJinUj0azs1JHewNx8A==
Date: Mon, 6 May 2013 07:17:26 +0000
Message-ID: <FC236DA6F2DA77449EF2D02DF4471A8D600780@xmb-rcd-x10.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.55.161.195]
Content-Type: multipart/alternative; boundary="_000_FC236DA6F2DA77449EF2D02DF4471A8D600780xmbrcdx10ciscocom_"
MIME-Version: 1.0
Subject: [CDNi] CDNI Logging - Series of Informal Meetings
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: Mon, 06 May 2013 07:17:33 -0000

--_000_FC236DA6F2DA77449EF2D02DF4471A8D600780xmbrcdx10ciscocom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi everyone,

(speaking as one of the cdni-logging co-authors)

We're in the process of revving up cdni-logging to reflect the Orlando disc=
ussions/conclusions. To maximise progress before Berlin, we'll run a series=
 of informal meetings to :
* collect feedback on interim versions of the I-D
* get input on the open items.

These informal meetings will be run as Webex sessions on:
* Wed 29 May 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, fo=
r 90 minutes
* Wed 5 June 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, fo=
r 90 minutes
* Wed 26 May 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, fo=
r 90 minutes

Please try attend and mark these slots in your calendar.

Cheers

Francois & cdni-logging co-authors

PS: Webex details below



=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Topic: IETF CDNI Logging - Informal Meeting
Date: Wednesday, May 29, 2013
Time: 5:00 pm, Europe Summer Time (Paris, GMT+02:00)
Meeting Number: 205 636 967
Password: cdni

-------------------------------------------------------
To join the meeting online(Now from mobile devices!)
-------------------------------------------------------
1. Go to https://cisco.webex.com/ciscosales/j.php?ED=3D225213752&UID=3D4843=
18167&PW=3DNNTMwZTVjNGRk&RT=3DMiMyMw%3D%3D
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: cdni
4. Click "Join".
5. If the meeting includes a teleconference, follow the instructions that a=
ppear on your screen.

-------------------------------------------------------
To join the audio conference only
-------------------------------------------------------
To receive a call back, provide your phone number when you join the meeting=
, or call the number below and enter the access code.
Call-in toll-free number (US/Canada): +1-866-432-9903
Call-in toll number (US/Canada): +1-408-525-6800
Toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restricti=
ons.pdf

Access code:205 636 967

CCP:+14085256800x205636967#

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D


Topic: IETF CDNI Logging - Informal Meeting
Date: Wednesday, June 5, 2013
Time: 5:00 pm, Europe Summer Time (Paris, GMT+02:00)
Meeting Number: 206 470 738
Password: cdni

-------------------------------------------------------
To join the meeting online(Now from mobile devices!)
-------------------------------------------------------
1. Go to https://cisco.webex.com/ciscosales/j.php?ED=3D225213782&UID=3D4843=
18167&PW=3DNMmQzODVmZjJm&RT=3DMiMyMw%3D%3D
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: cdni
4. Click "Join".
5. If the meeting includes a teleconference, follow the instructions that a=
ppear on your screen.

-------------------------------------------------------
To join the audio conference only
-------------------------------------------------------
To receive a call back, provide your phone number when you join the meeting=
, or call the number below and enter the access code.
Call-in toll-free number (US/Canada): +1-866-432-9903
Call-in toll number (US/Canada): +1-408-525-6800
Toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restricti=
ons.pdf

Access code:206 470 738

CCP:+14085256800x206470738#

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Topic: IETF CDNI Logging - Informal Meeting
Date: Wednesday, June 26, 2013
Time: 5:00 pm, Europe Summer Time (Paris, GMT+02:00)
Meeting Number: 208 330 914
Password: cdni

-------------------------------------------------------
To join the meeting online(Now from mobile devices!)
-------------------------------------------------------
1. Go to https://cisco.webex.com/ciscosales/j.php?ED=3D225213802&UID=3D4843=
18167&PW=3DNNzQ0ZmZmNjUz&RT=3DMiMyMw%3D%3D
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: cdni
4. Click "Join".
5. If the meeting includes a teleconference, follow the instructions that a=
ppear on your screen.

-------------------------------------------------------
To join the audio conference only
-------------------------------------------------------
To receive a call back, provide your phone number when you join the meeting=
, or call the number below and enter the access code.
Call-in toll-free number (US/Canada): +1-866-432-9903
Call-in toll number (US/Canada): +1-408-525-6800
Toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restricti=
ons.pdf

Access code:208 330 914

CCP:+14085256800x208330914#

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
IMPORTANT NOTICE: This WebEx service includes a feature that allows audio a=
nd any documents and other materials exchanged or viewed during the session=
 to be recorded. By joining this session, you automatically consent to such=
 recordings. If you do not consent to the recording, discuss your concerns =
with the meeting host prior to the start of the recording or do not join th=
e session. Please note that any such recordings may be subject to discovery=
 in the event of litigation.

--_000_FC236DA6F2DA77449EF2D02DF4471A8D600780xmbrcdx10ciscocom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <4F746DE43A9DC046AB2F7BF5E0423B6D@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>Hi everyone,</div>
<div><br>
</div>
<div>(speaking as one of the cdni-logging co-authors)</div>
<div><br>
</div>
<div>We're in the process of revving up cdni-logging to reflect the Orlando=
 discussions/conclusions. To maximise progress before Berlin, we'll run&nbs=
p;a series of informal meetings to :</div>
<div><span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>*&nbsp=
;collect feedback on&nbsp;interim versions of the I-D&nbsp;</div>
<div><span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>* get&=
nbsp;input on the open items.</div>
<div><br>
</div>
<div>These informal meetings will be run as Webex sessions on:</div>
<div><span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>* Wed =
29 May 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, for 90 m=
inutes</div>
<div><span class=3D"Apple-tab-span" style=3D"white-space: pre; "></span>* W=
ed 5 June 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, for 9=
0 minutes</div>
<div><span class=3D"Apple-tab-span" style=3D"white-space: pre; "></span>* W=
ed 26 May 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, for 9=
0 minutes<span class=3D"Apple-tab-span" style=3D"white-space:pre">
</span></div>
<div><br>
</div>
<div>Please try attend and mark these slots in your calendar.</div>
<div><br>
</div>
<div>Cheers</div>
<div><br>
</div>
<div>Francois &amp; cdni-logging co-authors</div>
<div><br>
</div>
<div>PS: Webex details below</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D<br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Genev=
a; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">Topic: IETF CDNI Logging - Informal Meeting&nbsp;</span>=
<br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; fon=
t-size: small; ">
<font face=3D"Tahoma" color=3D"#912604"><span style=3D"font-size: 16px; "><=
b>Date: Wednesday, May 29, 2013&nbsp;</b></span></font><br style=3D"font-fa=
mily: Tahoma, Arial, sans-serif, Helvetica, Geneva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">Time: 5:00 pm, Europe Summer Time (Paris, GMT&#43;02:00)=
&nbsp;</span><br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica=
, Geneva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">Meeting Number: 205 636 967&nbsp;</span><br style=3D"fon=
t-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; font-size: small; "=
>
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">Password: cdni&nbsp;</span><br style=3D"font-family: Tah=
oma, Arial, sans-serif, Helvetica, Geneva; font-size: small; ">
<br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; fon=
t-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">-------------------------------------------------------&=
nbsp;</span><br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica,=
 Geneva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">To join the meeting online(Now from mobile devices!)&nbs=
p;</span><br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Ge=
neva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">-------------------------------------------------------&=
nbsp;</span><br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica,=
 Geneva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">1. Go to&nbsp;</span><a href=3D"https://cisco.webex.com/=
ciscosales/j.php?ED=3D225213752&amp;UID=3D484318167&amp;PW=3DNNTMwZTVjNGRk&=
amp;RT=3DMiMyMw%3D%3D" target=3D"_blank" style=3D"font-family: Tahoma, Aria=
l, sans-serif, Helvetica, Geneva; font-size: small; ">https://cisco.webex.c=
om/ciscosales/j.php?ED=3D225213752&amp;UID=3D484318167&amp;PW=3DNNTMwZTVjNG=
Rk&amp;RT=3DMiMyMw%3D%3D</a><span style=3D"font-family: Tahoma, Arial, sans=
-serif, Helvetica, Geneva; font-size: small; ">&nbsp;</span><br style=3D"fo=
nt-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; font-size: small; =
">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">2. If requested, enter your name and email address.&nbsp=
;</span><br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Gen=
eva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">3. If a password is required, enter the meeting password=
: cdni&nbsp;</span><br style=3D"font-family: Tahoma, Arial, sans-serif, Hel=
vetica, Geneva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">4. Click &quot;Join&quot;.&nbsp;</span><br style=3D"font=
-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">5. If the meeting includes a teleconference, follow the =
instructions that appear on your screen.&nbsp;</span><br style=3D"font-fami=
ly: Tahoma, Arial, sans-serif, Helvetica, Geneva; font-size: small; ">
<br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; fon=
t-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">-------------------------------------------------------&=
nbsp;</span><br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica,=
 Geneva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">To join the audio conference only&nbsp;</span><br style=
=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; font-size: s=
mall; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">-------------------------------------------------------&=
nbsp;</span><br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica,=
 Geneva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">To receive a call back, provide your phone number when y=
ou join the meeting, or call the number below and enter the access code.&nb=
sp;</span><br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, G=
eneva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">Call-in toll-free number (US/Canada): &#43;1-866-432-990=
3&nbsp;</span><br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetic=
a, Geneva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">Call-in toll number (US/Canada): &#43;1-408-525-6800&nbs=
p;</span><br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Ge=
neva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">Toll-free dialing restrictions:&nbsp;</span><a href=3D"h=
ttp://www.webex.com/pdf/tollfree_restrictions.pdf" target=3D"_blank" style=
=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; font-size: s=
mall; ">http://www.webex.com/pdf/tollfree_restrictions.pdf</a><span style=
=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; font-size: s=
mall; ">&nbsp;</span><br style=3D"font-family: Tahoma, Arial, sans-serif, H=
elvetica, Geneva; font-size: small; ">
<br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; fon=
t-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">Access code:205 636 967&nbsp;</span><br style=3D"font-fa=
mily: Tahoma, Arial, sans-serif, Helvetica, Geneva; font-size: small; ">
<br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; fon=
t-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">CCP:&#43;14085256800x205636967#&nbsp;</span><br style=3D=
"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; font-size: smal=
l; ">
<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D<br>
<br>
<br>
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">Topic: IETF CDNI Logging - Informal Meeting&nbsp;</span>=
<br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; fon=
t-size: small; ">
<font color=3D"#912604" face=3D"Tahoma" style=3D"font-size: 16px;"><b>Date:=
 Wednesday, June 5, 2013&nbsp;</b></font><br style=3D"font-family: Tahoma, =
Arial, sans-serif, Helvetica, Geneva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">Time: 5:00 pm, Europe Summer Time (Paris, GMT&#43;02:00)=
&nbsp;</span><br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica=
, Geneva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">Meeting Number: 206 470 738&nbsp;</span><br style=3D"fon=
t-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; font-size: small; "=
>
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">Password: cdni&nbsp;</span><br style=3D"font-family: Tah=
oma, Arial, sans-serif, Helvetica, Geneva; font-size: small; ">
<br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; fon=
t-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">-------------------------------------------------------&=
nbsp;</span><br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica,=
 Geneva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">To join the meeting online(Now from mobile devices!)&nbs=
p;</span><br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Ge=
neva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">-------------------------------------------------------&=
nbsp;</span><br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica,=
 Geneva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">1. Go to&nbsp;</span><a href=3D"https://cisco.webex.com/=
ciscosales/j.php?ED=3D225213782&amp;UID=3D484318167&amp;PW=3DNMmQzODVmZjJm&=
amp;RT=3DMiMyMw%3D%3D" target=3D"_blank" style=3D"font-family: Tahoma, Aria=
l, sans-serif, Helvetica, Geneva; font-size: small; ">https://cisco.webex.c=
om/ciscosales/j.php?ED=3D225213782&amp;UID=3D484318167&amp;PW=3DNMmQzODVmZj=
Jm&amp;RT=3DMiMyMw%3D%3D</a><span style=3D"font-family: Tahoma, Arial, sans=
-serif, Helvetica, Geneva; font-size: small; ">&nbsp;</span><br style=3D"fo=
nt-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; font-size: small; =
">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">2. If requested, enter your name and email address.&nbsp=
;</span><br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Gen=
eva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">3. If a password is required, enter the meeting password=
: cdni&nbsp;</span><br style=3D"font-family: Tahoma, Arial, sans-serif, Hel=
vetica, Geneva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">4. Click &quot;Join&quot;.&nbsp;</span><br style=3D"font=
-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">5. If the meeting includes a teleconference, follow the =
instructions that appear on your screen.&nbsp;</span><br style=3D"font-fami=
ly: Tahoma, Arial, sans-serif, Helvetica, Geneva; font-size: small; ">
<br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; fon=
t-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">-------------------------------------------------------&=
nbsp;</span><br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica,=
 Geneva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">To join the audio conference only&nbsp;</span><br style=
=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; font-size: s=
mall; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">-------------------------------------------------------&=
nbsp;</span><br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica,=
 Geneva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">To receive a call back, provide your phone number when y=
ou join the meeting, or call the number below and enter the access code.&nb=
sp;</span><br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, G=
eneva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">Call-in toll-free number (US/Canada): &#43;1-866-432-990=
3&nbsp;</span><br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetic=
a, Geneva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">Call-in toll number (US/Canada): &#43;1-408-525-6800&nbs=
p;</span><br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Ge=
neva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">Toll-free dialing restrictions:&nbsp;</span><a href=3D"h=
ttp://www.webex.com/pdf/tollfree_restrictions.pdf" target=3D"_blank" style=
=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; font-size: s=
mall; ">http://www.webex.com/pdf/tollfree_restrictions.pdf</a><span style=
=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; font-size: s=
mall; ">&nbsp;</span><br style=3D"font-family: Tahoma, Arial, sans-serif, H=
elvetica, Geneva; font-size: small; ">
<br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; fon=
t-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">Access code:206 470 738&nbsp;</span><br style=3D"font-fa=
mily: Tahoma, Arial, sans-serif, Helvetica, Geneva; font-size: small; ">
<br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; fon=
t-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">CCP:&#43;14085256800x206470738#&nbsp;</span><br>
<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
<br>
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">Topic: IETF CDNI Logging - Informal Meeting&nbsp;</span>=
<br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; fon=
t-size: small; ">
<font color=3D"#912604" face=3D"Tahoma" style=3D"font-size: 16px;"><b>Date:=
 Wednesday, June 26, 2013&nbsp;</b></font><br style=3D"font-family: Tahoma,=
 Arial, sans-serif, Helvetica, Geneva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">Time: 5:00 pm, Europe Summer Time (Paris, GMT&#43;02:00)=
&nbsp;</span><br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica=
, Geneva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">Meeting Number: 208 330 914&nbsp;</span><br style=3D"fon=
t-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; font-size: small; "=
>
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">Password: cdni&nbsp;</span><br style=3D"font-family: Tah=
oma, Arial, sans-serif, Helvetica, Geneva; font-size: small; ">
<br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; fon=
t-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">-------------------------------------------------------&=
nbsp;</span><br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica,=
 Geneva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">To join the meeting online(Now from mobile devices!)&nbs=
p;</span><br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Ge=
neva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">-------------------------------------------------------&=
nbsp;</span><br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica,=
 Geneva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">1. Go to&nbsp;</span><a href=3D"https://cisco.webex.com/=
ciscosales/j.php?ED=3D225213802&amp;UID=3D484318167&amp;PW=3DNNzQ0ZmZmNjUz&=
amp;RT=3DMiMyMw%3D%3D" target=3D"_blank" style=3D"font-family: Tahoma, Aria=
l, sans-serif, Helvetica, Geneva; font-size: small; ">https://cisco.webex.c=
om/ciscosales/j.php?ED=3D225213802&amp;UID=3D484318167&amp;PW=3DNNzQ0ZmZmNj=
Uz&amp;RT=3DMiMyMw%3D%3D</a><span style=3D"font-family: Tahoma, Arial, sans=
-serif, Helvetica, Geneva; font-size: small; ">&nbsp;</span><br style=3D"fo=
nt-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; font-size: small; =
">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">2. If requested, enter your name and email address.&nbsp=
;</span><br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Gen=
eva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">3. If a password is required, enter the meeting password=
: cdni&nbsp;</span><br style=3D"font-family: Tahoma, Arial, sans-serif, Hel=
vetica, Geneva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">4. Click &quot;Join&quot;.&nbsp;</span><br style=3D"font=
-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">5. If the meeting includes a teleconference, follow the =
instructions that appear on your screen.&nbsp;</span><br style=3D"font-fami=
ly: Tahoma, Arial, sans-serif, Helvetica, Geneva; font-size: small; ">
<br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; fon=
t-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">-------------------------------------------------------&=
nbsp;</span><br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica,=
 Geneva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">To join the audio conference only&nbsp;</span><br style=
=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; font-size: s=
mall; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">-------------------------------------------------------&=
nbsp;</span><br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica,=
 Geneva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">To receive a call back, provide your phone number when y=
ou join the meeting, or call the number below and enter the access code.&nb=
sp;</span><br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, G=
eneva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">Call-in toll-free number (US/Canada): &#43;1-866-432-990=
3&nbsp;</span><br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetic=
a, Geneva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">Call-in toll number (US/Canada): &#43;1-408-525-6800&nbs=
p;</span><br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Ge=
neva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">Toll-free dialing restrictions:&nbsp;</span><a href=3D"h=
ttp://www.webex.com/pdf/tollfree_restrictions.pdf" target=3D"_blank" style=
=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; font-size: s=
mall; ">http://www.webex.com/pdf/tollfree_restrictions.pdf</a><span style=
=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; font-size: s=
mall; ">&nbsp;</span><br style=3D"font-family: Tahoma, Arial, sans-serif, H=
elvetica, Geneva; font-size: small; ">
<br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; fon=
t-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">Access code:208 330 914&nbsp;</span><br style=3D"font-fa=
mily: Tahoma, Arial, sans-serif, Helvetica, Geneva; font-size: small; ">
<br style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; fon=
t-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">CCP:&#43;14085256800x208330914#&nbsp;</span><br style=3D=
"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; font-size: smal=
l; ">
<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br style=3D"font-family: Tahoma, Ar=
ial, sans-serif, Helvetica, Geneva; font-size: small; ">
<span style=3D"font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; f=
ont-size: small; ">IMPORTANT NOTICE: This WebEx service includes a feature =
that allows audio and any documents and other materials exchanged or viewed=
 during the session to be recorded.
 By joining this session, you automatically consent to such recordings. If =
you do not consent to the recording, discuss your concerns with the meeting=
 host prior to the start of the recording or do not join the session. Pleas=
e note that any such recordings
 may be subject to discovery in the event of litigation.&nbsp;</span></div>
</body>
</html>

--_000_FC236DA6F2DA77449EF2D02DF4471A8D600780xmbrcdx10ciscocom_--

From emile.stephan@orange.com  Mon May  6 02:28:49 2013
Return-Path: <emile.stephan@orange.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 BB6FF21F85D6 for <cdni@ietfa.amsl.com>; Mon,  6 May 2013 02:28:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level: 
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_63=0.6, UNPARSEABLE_RELAY=0.001]
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 mdktV74h99Yp for <cdni@ietfa.amsl.com>; Mon,  6 May 2013 02:28:45 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id 1772C21F8F25 for <cdni@ietf.org>; Mon,  6 May 2013 02:28:44 -0700 (PDT)
Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm10.si.francetelecom.fr (ESMTP service) with ESMTP id E20A72641FF; Mon,  6 May 2013 11:28:43 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id C3A4C27C06E; Mon,  6 May 2013 11:28:43 +0200 (CEST)
Received: from PEXCVZYM14.corporate.adroot.infra.ftgroup ([fe80::a42f:c628:bc76:d592]) by PEXCVZYH02.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0328.009; Mon, 6 May 2013 11:28:42 +0200
From: <emile.stephan@orange.com>
To: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
Thread-Topic: CDNI Logging - Series of Informal Meetings
Thread-Index: AQHOSinCyYxSJinUj0azs1JHewNx8Jj34h8Q
Date: Mon, 6 May 2013 09:28:42 +0000
Message-ID: <32176_1367832523_518777CB_32176_694_1_5AE9CCAA1B4A2248AB61B4C7F0AD5FB906C34DC6@PEXCVZYM14.corporate.adroot.infra.ftgroup>
References: <FC236DA6F2DA77449EF2D02DF4471A8D600780@xmb-rcd-x10.cisco.com>
In-Reply-To: <FC236DA6F2DA77449EF2D02DF4471A8D600780@xmb-rcd-x10.cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.197.38.5]
Content-Type: multipart/alternative; boundary="_000_5AE9CCAA1B4A2248AB61B4C7F0AD5FB906C34DC6PEXCVZYM14corpo_"
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.5.2.64815
Cc: "cdni@ietf.org" <cdni@ietf.org>
Subject: Re: [CDNi] CDNI Logging - Series of Informal Meetings
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: Mon, 06 May 2013 09:28:49 -0000

--_000_5AE9CCAA1B4A2248AB61B4C7F0AD5FB906C34DC6PEXCVZYM14corpo_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Francois,

Just in case, is the third meeting planned for the 26 of June?

Regards
Emile

De : cdni-bounces@ietf.org [mailto:cdni-bounces@ietf.org] De la part de Fra=
ncois Le Faucheur (flefauch)
Envoy=E9 : lundi 6 mai 2013 09:17
=C0 : cdni@ietf.org
Objet : [CDNi] CDNI Logging - Series of Informal Meetings

Hi everyone,

(speaking as one of the cdni-logging co-authors)

We're in the process of revving up cdni-logging to reflect the Orlando disc=
ussions/conclusions. To maximise progress before Berlin, we'll run a series=
 of informal meetings to :
* collect feedback on interim versions of the I-D
* get input on the open items.

These informal meetings will be run as Webex sessions on:
* Wed 29 May 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, fo=
r 90 minutes
* Wed 5 June 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, fo=
r 90 minutes
* Wed 26 May 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, fo=
r 90 minutes

Please try attend and mark these slots in your calendar.

Cheers

Francois & cdni-logging co-authors

PS: Webex details below



=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Topic: IETF CDNI Logging - Informal Meeting
Date: Wednesday, May 29, 2013
Time: 5:00 pm, Europe Summer Time (Paris, GMT+02:00)
Meeting Number: 205 636 967
Password: cdni

-------------------------------------------------------
To join the meeting online(Now from mobile devices!)
-------------------------------------------------------
1. Go to https://cisco.webex.com/ciscosales/j.php?ED=3D225213752&UID=3D4843=
18167&PW=3DNNTMwZTVjNGRk&RT=3DMiMyMw%3D%3D
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: cdni
4. Click "Join".
5. If the meeting includes a teleconference, follow the instructions that a=
ppear on your screen.

-------------------------------------------------------
To join the audio conference only
-------------------------------------------------------
To receive a call back, provide your phone number when you join the meeting=
, or call the number below and enter the access code.
Call-in toll-free number (US/Canada): +1-866-432-9903
Call-in toll number (US/Canada): +1-408-525-6800
Toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restricti=
ons.pdf

Access code:205 636 967

CCP:+14085256800x205636967#

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D


Topic: IETF CDNI Logging - Informal Meeting
Date: Wednesday, June 5, 2013
Time: 5:00 pm, Europe Summer Time (Paris, GMT+02:00)
Meeting Number: 206 470 738
Password: cdni

-------------------------------------------------------
To join the meeting online(Now from mobile devices!)
-------------------------------------------------------
1. Go to https://cisco.webex.com/ciscosales/j.php?ED=3D225213782&UID=3D4843=
18167&PW=3DNMmQzODVmZjJm&RT=3DMiMyMw%3D%3D
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: cdni
4. Click "Join".
5. If the meeting includes a teleconference, follow the instructions that a=
ppear on your screen.

-------------------------------------------------------
To join the audio conference only
-------------------------------------------------------
To receive a call back, provide your phone number when you join the meeting=
, or call the number below and enter the access code.
Call-in toll-free number (US/Canada): +1-866-432-9903
Call-in toll number (US/Canada): +1-408-525-6800
Toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restricti=
ons.pdf

Access code:206 470 738

CCP:+14085256800x206470738#

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Topic: IETF CDNI Logging - Informal Meeting
Date: Wednesday, June 26, 2013
Time: 5:00 pm, Europe Summer Time (Paris, GMT+02:00)
Meeting Number: 208 330 914
Password: cdni

-------------------------------------------------------
To join the meeting online(Now from mobile devices!)
-------------------------------------------------------
1. Go to https://cisco.webex.com/ciscosales/j.php?ED=3D225213802&UID=3D4843=
18167&PW=3DNNzQ0ZmZmNjUz&RT=3DMiMyMw%3D%3D
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: cdni
4. Click "Join".
5. If the meeting includes a teleconference, follow the instructions that a=
ppear on your screen.

-------------------------------------------------------
To join the audio conference only
-------------------------------------------------------
To receive a call back, provide your phone number when you join the meeting=
, or call the number below and enter the access code.
Call-in toll-free number (US/Canada): +1-866-432-9903
Call-in toll number (US/Canada): +1-408-525-6800
Toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restricti=
ons.pdf

Access code:208 330 914

CCP:+14085256800x208330914#

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
IMPORTANT NOTICE: This WebEx service includes a feature that allows audio a=
nd any documents and other materials exchanged or viewed during the session=
 to be recorded. By joining this session, you automatically consent to such=
 recordings. If you do not consent to the recording, discuss your concerns =
with the meeting host prior to the start of the recording or do not join th=
e session. Please note that any such recordings may be subject to discovery=
 in the event of litigation.

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for message=
s that have been modified, changed or falsified.
Thank you.


--_000_5AE9CCAA1B4A2248AB61B4C7F0AD5FB906C34DC6PEXCVZYM14corpo_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.apple-tab-span
	{mso-style-name:apple-tab-span;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"FR" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hi Francois,<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Just in case, is the third meet=
ing planned for the 26 of June?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Regards<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Emile<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">De&nbsp;:</span></b><span style=3D"fo=
nt-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> cdni=
-bounces@ietf.org [mailto:cdni-bounces@ietf.org]
<b>De la part de</b> Francois Le Faucheur (flefauch)<br>
<b>Envoy=E9&nbsp;:</b> lundi 6 mai 2013 09:17<br>
<b>=C0&nbsp;:</b> cdni@ietf.org<br>
<b>Objet&nbsp;:</b> [CDNi] CDNI Logging - Series of Informal Meetings<o:p><=
/o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">Hi everyone,<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">(speaking as one of the cdni-logging co-authors)<o:p=
></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">We're in the process of revving up cdni-logging to r=
eflect the Orlando discussions/conclusions. To maximise progress before Ber=
lin, we'll run&nbsp;a series of informal meetings to :<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">*&nbsp;collect feedback on&nbsp;interim versions of =
the I-D&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">* get&nbsp;input on the open items.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">These informal meetings will be run as Webex session=
s on:<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">* Wed 29 May 2013, at 08:0 Pacific Time =3D 17:00 Ce=
ntral European Time, for 90 minutes<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">* Wed 5 June 2013, at 08:0 Pacific Time =3D 17:00 Ce=
ntral European Time, for 90 minutes<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">* Wed 26 May 2013, at 08:0 Pacific Time =3D 17:00 Ce=
ntral European Time, for 90 minutes<span class=3D"apple-tab-span"><o:p></o:=
p></span></p>
</div>
<p class=3D"MsoNormal"><o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Please try attend and mark these slots in your calen=
dar.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Cheers<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Francois &amp; cdni-logging co-authors<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">PS: Webex details below<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D<span style=3D"font-family:&quot;Tahoma&quot;,&quot=
;sans-serif&quot;"><br>
Topic: IETF CDNI Logging - Informal Meeting&nbsp;<br>
<b><span style=3D"color:#912604">Date: Wednesday, May 29, 2013&nbsp;</span>=
</b><br>
Time: 5:00 pm, Europe Summer Time (Paris, GMT&#43;02:00)&nbsp;<br>
Meeting Number: 205 636 967&nbsp;<br>
Password: cdni&nbsp;<br>
<br>
-------------------------------------------------------&nbsp;<br>
To join the meeting online(Now from mobile devices!)&nbsp;<br>
-------------------------------------------------------&nbsp;<br>
1. Go to&nbsp;</span><a href=3D"https://cisco.webex.com/ciscosales/j.php?ED=
=3D225213752&amp;UID=3D484318167&amp;PW=3DNNTMwZTVjNGRk&amp;RT=3DMiMyMw%3D%=
3D" target=3D"_blank"><span style=3D"font-family:&quot;Tahoma&quot;,&quot;s=
ans-serif&quot;">https://cisco.webex.com/ciscosales/j.php?ED=3D225213752&am=
p;UID=3D484318167&amp;PW=3DNNTMwZTVjNGRk&amp;RT=3DMiMyMw%3D%3D</span></a><s=
pan style=3D"font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">&nbsp;<=
br>
2. If requested, enter your name and email address.&nbsp;<br>
3. If a password is required, enter the meeting password: cdni&nbsp;<br>
4. Click &quot;Join&quot;.&nbsp;<br>
5. If the meeting includes a teleconference, follow the instructions that a=
ppear on your screen.&nbsp;<br>
<br>
-------------------------------------------------------&nbsp;<br>
To join the audio conference only&nbsp;<br>
-------------------------------------------------------&nbsp;<br>
To receive a call back, provide your phone number when you join the meeting=
, or call the number below and enter the access code.&nbsp;<br>
Call-in toll-free number (US/Canada): &#43;1-866-432-9903&nbsp;<br>
Call-in toll number (US/Canada): &#43;1-408-525-6800&nbsp;<br>
Toll-free dialing restrictions:&nbsp;</span><a href=3D"http://www.webex.com=
/pdf/tollfree_restrictions.pdf" target=3D"_blank"><span style=3D"font-famil=
y:&quot;Tahoma&quot;,&quot;sans-serif&quot;">http://www.webex.com/pdf/tollf=
ree_restrictions.pdf</span></a><span style=3D"font-family:&quot;Tahoma&quot=
;,&quot;sans-serif&quot;">&nbsp;<br>
<br>
Access code:205 636 967&nbsp;<br>
<br>
CCP:&#43;14085256800x205636967#&nbsp;<br>
</span><br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D<br>
<br>
<br>
<span style=3D"font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">Topic=
: IETF CDNI Logging - Informal Meeting&nbsp;<br>
<b><span style=3D"color:#912604">Date: Wednesday, June 5, 2013&nbsp;</span>=
</b><br>
Time: 5:00 pm, Europe Summer Time (Paris, GMT&#43;02:00)&nbsp;<br>
Meeting Number: 206 470 738&nbsp;<br>
Password: cdni&nbsp;<br>
<br>
-------------------------------------------------------&nbsp;<br>
To join the meeting online(Now from mobile devices!)&nbsp;<br>
-------------------------------------------------------&nbsp;<br>
1. Go to&nbsp;</span><a href=3D"https://cisco.webex.com/ciscosales/j.php?ED=
=3D225213782&amp;UID=3D484318167&amp;PW=3DNMmQzODVmZjJm&amp;RT=3DMiMyMw%3D%=
3D" target=3D"_blank"><span style=3D"font-family:&quot;Tahoma&quot;,&quot;s=
ans-serif&quot;">https://cisco.webex.com/ciscosales/j.php?ED=3D225213782&am=
p;UID=3D484318167&amp;PW=3DNMmQzODVmZjJm&amp;RT=3DMiMyMw%3D%3D</span></a><s=
pan style=3D"font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">&nbsp;<=
br>
2. If requested, enter your name and email address.&nbsp;<br>
3. If a password is required, enter the meeting password: cdni&nbsp;<br>
4. Click &quot;Join&quot;.&nbsp;<br>
5. If the meeting includes a teleconference, follow the instructions that a=
ppear on your screen.&nbsp;<br>
<br>
-------------------------------------------------------&nbsp;<br>
To join the audio conference only&nbsp;<br>
-------------------------------------------------------&nbsp;<br>
To receive a call back, provide your phone number when you join the meeting=
, or call the number below and enter the access code.&nbsp;<br>
Call-in toll-free number (US/Canada): &#43;1-866-432-9903&nbsp;<br>
Call-in toll number (US/Canada): &#43;1-408-525-6800&nbsp;<br>
Toll-free dialing restrictions:&nbsp;</span><a href=3D"http://www.webex.com=
/pdf/tollfree_restrictions.pdf" target=3D"_blank"><span style=3D"font-famil=
y:&quot;Tahoma&quot;,&quot;sans-serif&quot;">http://www.webex.com/pdf/tollf=
ree_restrictions.pdf</span></a><span style=3D"font-family:&quot;Tahoma&quot=
;,&quot;sans-serif&quot;">&nbsp;<br>
<br>
Access code:206 470 738&nbsp;<br>
<br>
CCP:&#43;14085256800x206470738#&nbsp;</span><br>
<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
<br>
<span style=3D"font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">Topic=
: IETF CDNI Logging - Informal Meeting&nbsp;<br>
<b><span style=3D"color:#912604">Date: Wednesday, June 26, 2013&nbsp;</span=
></b><br>
Time: 5:00 pm, Europe Summer Time (Paris, GMT&#43;02:00)&nbsp;<br>
Meeting Number: 208 330 914&nbsp;<br>
Password: cdni&nbsp;<br>
<br>
-------------------------------------------------------&nbsp;<br>
To join the meeting online(Now from mobile devices!)&nbsp;<br>
-------------------------------------------------------&nbsp;<br>
1. Go to&nbsp;</span><a href=3D"https://cisco.webex.com/ciscosales/j.php?ED=
=3D225213802&amp;UID=3D484318167&amp;PW=3DNNzQ0ZmZmNjUz&amp;RT=3DMiMyMw%3D%=
3D" target=3D"_blank"><span style=3D"font-family:&quot;Tahoma&quot;,&quot;s=
ans-serif&quot;">https://cisco.webex.com/ciscosales/j.php?ED=3D225213802&am=
p;UID=3D484318167&amp;PW=3DNNzQ0ZmZmNjUz&amp;RT=3DMiMyMw%3D%3D</span></a><s=
pan style=3D"font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">&nbsp;<=
br>
2. If requested, enter your name and email address.&nbsp;<br>
3. If a password is required, enter the meeting password: cdni&nbsp;<br>
4. Click &quot;Join&quot;.&nbsp;<br>
5. If the meeting includes a teleconference, follow the instructions that a=
ppear on your screen.&nbsp;<br>
<br>
-------------------------------------------------------&nbsp;<br>
To join the audio conference only&nbsp;<br>
-------------------------------------------------------&nbsp;<br>
To receive a call back, provide your phone number when you join the meeting=
, or call the number below and enter the access code.&nbsp;<br>
Call-in toll-free number (US/Canada): &#43;1-866-432-9903&nbsp;<br>
Call-in toll number (US/Canada): &#43;1-408-525-6800&nbsp;<br>
Toll-free dialing restrictions:&nbsp;</span><a href=3D"http://www.webex.com=
/pdf/tollfree_restrictions.pdf" target=3D"_blank"><span style=3D"font-famil=
y:&quot;Tahoma&quot;,&quot;sans-serif&quot;">http://www.webex.com/pdf/tollf=
ree_restrictions.pdf</span></a><span style=3D"font-family:&quot;Tahoma&quot=
;,&quot;sans-serif&quot;">&nbsp;<br>
<br>
Access code:208 330 914&nbsp;<br>
<br>
CCP:&#43;14085256800x208330914#&nbsp;<br>
</span><br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<span style=3D"font-family:&quot;Tah=
oma&quot;,&quot;sans-serif&quot;"><br>
IMPORTANT NOTICE: This WebEx service includes a feature that allows audio a=
nd any documents and other materials exchanged or viewed during the session=
 to be recorded. By joining this session, you automatically consent to such=
 recordings. If you do not consent
 to the recording, discuss your concerns with the meeting host prior to the=
 start of the recording or do not join the session. Please note that any su=
ch recordings may be subject to discovery in the event of litigation.&nbsp;=
</span><o:p></o:p></p>
</div>
</div>
<PRE>______________________________________________________________________=
___________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for message=
s that have been modified, changed or falsified.
Thank you.
</PRE></body>
</html>

--_000_5AE9CCAA1B4A2248AB61B4C7F0AD5FB906C34DC6PEXCVZYM14corpo_--

From flefauch@cisco.com  Mon May  6 02:36:16 2013
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 4257821F8FA1 for <cdni@ietfa.amsl.com>; Mon,  6 May 2013 02:36:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.998
X-Spam-Level: 
X-Spam-Status: No, score=-9.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_63=0.6, 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 TtbjzypUw0zZ for <cdni@ietfa.amsl.com>; Mon,  6 May 2013 02:36:11 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 1A18F21F8F62 for <cdni@ietf.org>; Mon,  6 May 2013 02:36:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=25482; q=dns/txt; s=iport; t=1367832971; x=1369042571; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=C12iBd5Pxv/YvN93ldroxhqsgIeYFiG41YHbkvQ2olE=; b=MNtABn79nNkiIAr5RWmytUJduRP6p2Rj1W2DuPE9asOmMYrX1bVK2BfM SFLbNvCKa0L/L+cZhrrhXaYy844jh032oTMiPgB6kVHKlm3H0OAGrek8F ifcVdXnEApIzZUhoKDpvThvl37lUxoT2uiJ5dSDCWmETjdZZxvLZmj1Lx c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmIFALJ4h1GtJXG//2dsb2JhbAA2FwOCQ0Q3vwKBBRZtB4IgAQECAmYCIQIBCBQOCgQIBAMHMhQQAQIBAxMIiAQMM7Mfi2GNbxt2IAELAQoBEQeCWmEDqGKCPFGBcjU
X-IronPort-AV: E=Sophos;i="4.87,620,1363132800";  d="scan'208,217";a="206830966"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-6.cisco.com with ESMTP; 06 May 2013 09:36:10 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id r469aA7G013076 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <cdni@ietf.org>; Mon, 6 May 2013 09:36:10 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.56]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.02.0318.004; Mon, 6 May 2013 04:36:10 -0500
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "cdni@ietf.org" <cdni@ietf.org>
Thread-Topic: CDNI Logging - Series of Informal Meetings
Thread-Index: AQHOSinCyYxSJinUj0azs1JHewNx8Jj34h8QgABXo4A=
Date: Mon, 6 May 2013 09:36:09 +0000
Message-ID: <FC236DA6F2DA77449EF2D02DF4471A8D60161E@xmb-rcd-x10.cisco.com>
References: <FC236DA6F2DA77449EF2D02DF4471A8D600780@xmb-rcd-x10.cisco.com> <32176_1367832523_518777CB_32176_694_1_5AE9CCAA1B4A2248AB61B4C7F0AD5FB906C34DC6@PEXCVZYM14.corporate.adroot.infra.ftgroup>
In-Reply-To: <32176_1367832523_518777CB_32176_694_1_5AE9CCAA1B4A2248AB61B4C7F0AD5FB906C34DC6@PEXCVZYM14.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.55.161.195]
Content-Type: multipart/alternative; boundary="_000_FC236DA6F2DA77449EF2D02DF4471A8D60161Exmbrcdx10ciscocom_"
MIME-Version: 1.0
Subject: Re: [CDNi] CDNI Logging - Series of Informal Meetings
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: Mon, 06 May 2013 09:36:16 -0000

--_000_FC236DA6F2DA77449EF2D02DF4471A8D60161Exmbrcdx10ciscocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Oops =85 correcting the typo pointed out by Emile in the last date:

These informal meetings will be run as Webex sessions on:
* Wed 29 May 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, fo=
r 90 minutes
* Wed 5 June 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, fo=
r 90 minutes
* Wed 26 June 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, f=
or 90 minutes

Francois

On 6 May 2013, at 11:28, emile.stephan@orange.com<mailto:emile.stephan@oran=
ge.com> wrote:

Hi Francois,

Just in case, is the third meeting planned for the 26 of June?

Regards
Emile

De : cdni-bounces@ietf.org<mailto:cdni-bounces@ietf.org> [mailto:cdni-bounc=
es@ietf.org<mailto:bounces@ietf.org>] De la part de Francois Le Faucheur (f=
lefauch)
Envoy=E9 : lundi 6 mai 2013 09:17
=C0 : cdni@ietf.org<mailto:cdni@ietf.org>
Objet : [CDNi] CDNI Logging - Series of Informal Meetings

Hi everyone,

(speaking as one of the cdni-logging co-authors)

We're in the process of revving up cdni-logging to reflect the Orlando disc=
ussions/conclusions. To maximise progress before Berlin, we'll run a series=
 of informal meetings to :
* collect feedback on interim versions of the I-D
* get input on the open items.

These informal meetings will be run as Webex sessions on:
* Wed 29 May 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, fo=
r 90 minutes
* Wed 5 June 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, fo=
r 90 minutes
* Wed 26 May 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, fo=
r 90 minutes

Please try attend and mark these slots in your calendar.

Cheers

Francois & cdni-logging co-authors

PS: Webex details below



=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Topic: IETF CDNI Logging - Informal Meeting
Date: Wednesday, May 29, 2013
Time: 5:00 pm, Europe Summer Time (Paris, GMT+02:00)
Meeting Number: 205 636 967
Password: cdni

-------------------------------------------------------
To join the meeting online(Now from mobile devices!)
-------------------------------------------------------
1. Go to https://cisco.webex.com/ciscosales/j.php?ED=3D225213752&UID=3D4843=
18167&PW=3DNNTMwZTVjNGRk&RT=3DMiMyMw%3D%3D
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: cdni
4. Click "Join".
5. If the meeting includes a teleconference, follow the instructions that a=
ppear on your screen.

-------------------------------------------------------
To join the audio conference only
-------------------------------------------------------
To receive a call back, provide your phone number when you join the meeting=
, or call the number below and enter the access code.
Call-in toll-free number (US/Canada): +1-866-432-9903
Call-in toll number (US/Canada): +1-408-525-6800
Toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restricti=
ons.pdf

Access code:205 636 967

CCP:+14085256800x205636967#

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D


Topic: IETF CDNI Logging - Informal Meeting
Date: Wednesday, June 5, 2013
Time: 5:00 pm, Europe Summer Time (Paris, GMT+02:00)
Meeting Number: 206 470 738
Password: cdni

-------------------------------------------------------
To join the meeting online(Now from mobile devices!)
-------------------------------------------------------
1. Go to https://cisco.webex.com/ciscosales/j.php?ED=3D225213782&UID=3D4843=
18167&PW=3DNMmQzODVmZjJm&RT=3DMiMyMw%3D%3D
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: cdni
4. Click "Join".
5. If the meeting includes a teleconference, follow the instructions that a=
ppear on your screen.

-------------------------------------------------------
To join the audio conference only
-------------------------------------------------------
To receive a call back, provide your phone number when you join the meeting=
, or call the number below and enter the access code.
Call-in toll-free number (US/Canada): +1-866-432-9903
Call-in toll number (US/Canada): +1-408-525-6800
Toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restricti=
ons.pdf

Access code:206 470 738

CCP:+14085256800x206470738#

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Topic: IETF CDNI Logging - Informal Meeting
Date: Wednesday, June 26, 2013
Time: 5:00 pm, Europe Summer Time (Paris, GMT+02:00)
Meeting Number: 208 330 914
Password: cdni

-------------------------------------------------------
To join the meeting online(Now from mobile devices!)
-------------------------------------------------------
1. Go to https://cisco.webex.com/ciscosales/j.php?ED=3D225213802&UID=3D4843=
18167&PW=3DNNzQ0ZmZmNjUz&RT=3DMiMyMw%3D%3D
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: cdni
4. Click "Join".
5. If the meeting includes a teleconference, follow the instructions that a=
ppear on your screen.

-------------------------------------------------------
To join the audio conference only
-------------------------------------------------------
To receive a call back, provide your phone number when you join the meeting=
, or call the number below and enter the access code.
Call-in toll-free number (US/Canada): +1-866-432-9903
Call-in toll number (US/Canada): +1-408-525-6800
Toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restricti=
ons.pdf

Access code:208 330 914

CCP:+14085256800x208330914#

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
IMPORTANT NOTICE: This WebEx service includes a feature that allows audio a=
nd any documents and other materials exchanged or viewed during the session=
 to be recorded. By joining this session, you automatically consent to such=
 recordings. If you do not consent to the recording, discuss your concerns =
with the meeting host prior to the start of the recording or do not join th=
e session. Please note that any such recordings may be subject to discovery=
 in the event of litigation.

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for message=
s that have been modified, changed or falsified.
Thank you.



--_000_FC236DA6F2DA77449EF2D02DF4471A8D60161Exmbrcdx10ciscocom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <C2D447994112344FAE7374C3713AA6D1@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<base href=3D"x-msg://829/">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>Oops =85 correcting the typo pointed out by Emile in the last date:</d=
iv>
<div><br>
</div>
<div>These informal meetings will be run as Webex sessions on:<br>
* Wed 29 May 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, fo=
r 90 minutes<br>
* Wed 5 June 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, fo=
r 90 minutes<br>
* Wed 26 June 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, f=
or 90 minutes</div>
<div><br>
</div>
<div>Francois</div>
<br>
<div>
<div>On 6 May 2013, at 11:28, <a href=3D"mailto:emile.stephan@orange.com">e=
mile.stephan@orange.com</a> wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div lang=3D"FR" link=3D"blue" vlink=3D"purple" style=3D"font-family: Helve=
tica; font-size: medium; font-style: normal; font-variant: normal; font-wei=
ght: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-=
align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: n=
ormal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webki=
t-text-stroke-width: 0px; ">
<div class=3D"WordSection1" style=3D"page: WordSection1; ">
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<span lang=3D"EN-US">Hi Francois,<o:p></o:p></span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<span lang=3D"EN-US">&nbsp;</span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<span lang=3D"EN-US">Just in case, is the third meeting planned for the 26 =
of June?<o:p></o:p></span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<span lang=3D"EN-US" style=3D"font-size: 11pt; font-family: Calibri, sans-s=
erif; color: rgb(31, 73, 125); ">&nbsp;</span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<span lang=3D"EN-US">Regards<o:p></o:p></span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<span lang=3D"EN-US">Emile<o:p></o:p></span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<span lang=3D"EN-US" style=3D"font-size: 11pt; font-family: Calibri, sans-s=
erif; color: rgb(31, 73, 125); ">&nbsp;</span></div>
<div>
<div style=3D"border-style: solid none none; border-top-width: 1pt; border-=
top-color: rgb(181, 196, 223); padding: 3pt 0cm 0cm; ">
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<b><span style=3D"font-size: 10pt; font-family: Tahoma, sans-serif; ">De&nb=
sp;:</span></b><span style=3D"font-size: 10pt; font-family: Tahoma, sans-se=
rif; "><span class=3D"Apple-converted-space">&nbsp;</span><a href=3D"mailto=
:cdni-bounces@ietf.org" style=3D"color: purple; text-decoration: underline;=
 ">cdni-bounces@ietf.org</a><span class=3D"Apple-converted-space">&nbsp;</s=
pan>[mailto:cdni-<a href=3D"mailto:bounces@ietf.org" style=3D"color: purple=
; text-decoration: underline; ">bounces@ietf.org</a>]<span class=3D"Apple-c=
onverted-space">&nbsp;</span><b>De
 la part de</b><span class=3D"Apple-converted-space">&nbsp;</span>Francois =
Le Faucheur (flefauch)<br>
<b>Envoy=E9&nbsp;:</b><span class=3D"Apple-converted-space">&nbsp;</span>lu=
ndi 6 mai 2013 09:17<br>
<b>=C0&nbsp;:</b><span class=3D"Apple-converted-space">&nbsp;</span><a href=
=3D"mailto:cdni@ietf.org" style=3D"color: purple; text-decoration: underlin=
e; ">cdni@ietf.org</a><br>
<b>Objet&nbsp;:</b><span class=3D"Apple-converted-space">&nbsp;</span>[CDNi=
] CDNI Logging - Series of Informal Meetings<o:p></o:p></span></div>
</div>
</div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<o:p>&nbsp;</o:p></div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
Hi everyone,<o:p></o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<o:p>&nbsp;</o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
(speaking as one of the cdni-logging co-authors)<o:p></o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<o:p>&nbsp;</o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
We're in the process of revving up cdni-logging to reflect the Orlando disc=
ussions/conclusions. To maximise progress before Berlin, we'll run&nbsp;a s=
eries of informal meetings to :<o:p></o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
*&nbsp;collect feedback on&nbsp;interim versions of the I-D&nbsp;<o:p></o:p=
></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
* get&nbsp;input on the open items.<o:p></o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<o:p>&nbsp;</o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
These informal meetings will be run as Webex sessions on:<o:p></o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
* Wed 29 May 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, fo=
r 90 minutes<o:p></o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
* Wed 5 June 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, fo=
r 90 minutes<o:p></o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
* Wed 26 May 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, fo=
r 90 minutes<span class=3D"apple-tab-span"><o:p></o:p></span></div>
</div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<o:p></o:p></div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<o:p>&nbsp;</o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
Please try attend and mark these slots in your calendar.<o:p></o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<o:p>&nbsp;</o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
Cheers<o:p></o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<o:p>&nbsp;</o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
Francois &amp; cdni-logging co-authors<o:p></o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<o:p>&nbsp;</o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
PS: Webex details below<o:p></o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<o:p>&nbsp;</o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<o:p>&nbsp;</o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<o:p>&nbsp;</o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
<span style=3D"font-family: Tahoma, sans-serif; "><br>
Topic: IETF CDNI Logging - Informal Meeting&nbsp;<br>
<b><span style=3D"color: rgb(145, 38, 4); ">Date: Wednesday, May 29, 2013&n=
bsp;</span></b><br>
Time: 5:00 pm, Europe Summer Time (Paris, GMT&#43;02:00)&nbsp;<br>
Meeting Number: 205 636 967&nbsp;<br>
Password: cdni&nbsp;<br>
<br>
-------------------------------------------------------&nbsp;<br>
To join the meeting online(Now from mobile devices!)&nbsp;<br>
-------------------------------------------------------&nbsp;<br>
1. Go to&nbsp;</span><a href=3D"https://cisco.webex.com/ciscosales/j.php?ED=
=3D225213752&amp;UID=3D484318167&amp;PW=3DNNTMwZTVjNGRk&amp;RT=3DMiMyMw%3D%=
3D" target=3D"_blank" style=3D"color: purple; text-decoration: underline; "=
><span style=3D"font-family: Tahoma, sans-serif; ">https://cisco.webex.com/=
ciscosales/j.php?ED=3D225213752&amp;UID=3D484318167&amp;PW=3DNNTMwZTVjNGRk&=
amp;RT=3DMiMyMw%3D%3D</span></a><span style=3D"font-family: Tahoma, sans-se=
rif; ">&nbsp;<br>
2. If requested, enter your name and email address.&nbsp;<br>
3. If a password is required, enter the meeting password: cdni&nbsp;<br>
4. Click &quot;Join&quot;.&nbsp;<br>
5. If the meeting includes a teleconference, follow the instructions that a=
ppear on your screen.&nbsp;<br>
<br>
-------------------------------------------------------&nbsp;<br>
To join the audio conference only&nbsp;<br>
-------------------------------------------------------&nbsp;<br>
To receive a call back, provide your phone number when you join the meeting=
, or call the number below and enter the access code.&nbsp;<br>
Call-in toll-free number (US/Canada): &#43;1-866-432-9903&nbsp;<br>
Call-in toll number (US/Canada): &#43;1-408-525-6800&nbsp;<br>
Toll-free dialing restrictions:&nbsp;</span><a href=3D"http://www.webex.com=
/pdf/tollfree_restrictions.pdf" target=3D"_blank" style=3D"color: purple; t=
ext-decoration: underline; "><span style=3D"font-family: Tahoma, sans-serif=
; ">http://www.webex.com/pdf/tollfree_restrictions.pdf</span></a><span styl=
e=3D"font-family: Tahoma, sans-serif; ">&nbsp;<br>
<br>
Access code:205 636 967&nbsp;<br>
<br>
CCP:&#43;14085256800x205636967#&nbsp;<br>
</span><br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D<br>
<br>
<br>
<span style=3D"font-family: Tahoma, sans-serif; ">Topic: IETF CDNI Logging =
- Informal Meeting&nbsp;<br>
<b><span style=3D"color: rgb(145, 38, 4); ">Date: Wednesday, June 5, 2013&n=
bsp;</span></b><br>
Time: 5:00 pm, Europe Summer Time (Paris, GMT&#43;02:00)&nbsp;<br>
Meeting Number: 206 470 738&nbsp;<br>
Password: cdni&nbsp;<br>
<br>
-------------------------------------------------------&nbsp;<br>
To join the meeting online(Now from mobile devices!)&nbsp;<br>
-------------------------------------------------------&nbsp;<br>
1. Go to&nbsp;</span><a href=3D"https://cisco.webex.com/ciscosales/j.php?ED=
=3D225213782&amp;UID=3D484318167&amp;PW=3DNMmQzODVmZjJm&amp;RT=3DMiMyMw%3D%=
3D" target=3D"_blank" style=3D"color: purple; text-decoration: underline; "=
><span style=3D"font-family: Tahoma, sans-serif; ">https://cisco.webex.com/=
ciscosales/j.php?ED=3D225213782&amp;UID=3D484318167&amp;PW=3DNMmQzODVmZjJm&=
amp;RT=3DMiMyMw%3D%3D</span></a><span style=3D"font-family: Tahoma, sans-se=
rif; ">&nbsp;<br>
2. If requested, enter your name and email address.&nbsp;<br>
3. If a password is required, enter the meeting password: cdni&nbsp;<br>
4. Click &quot;Join&quot;.&nbsp;<br>
5. If the meeting includes a teleconference, follow the instructions that a=
ppear on your screen.&nbsp;<br>
<br>
-------------------------------------------------------&nbsp;<br>
To join the audio conference only&nbsp;<br>
-------------------------------------------------------&nbsp;<br>
To receive a call back, provide your phone number when you join the meeting=
, or call the number below and enter the access code.&nbsp;<br>
Call-in toll-free number (US/Canada): &#43;1-866-432-9903&nbsp;<br>
Call-in toll number (US/Canada): &#43;1-408-525-6800&nbsp;<br>
Toll-free dialing restrictions:&nbsp;</span><a href=3D"http://www.webex.com=
/pdf/tollfree_restrictions.pdf" target=3D"_blank" style=3D"color: purple; t=
ext-decoration: underline; "><span style=3D"font-family: Tahoma, sans-serif=
; ">http://www.webex.com/pdf/tollfree_restrictions.pdf</span></a><span styl=
e=3D"font-family: Tahoma, sans-serif; ">&nbsp;<br>
<br>
Access code:206 470 738&nbsp;<br>
<br>
CCP:&#43;14085256800x206470738#&nbsp;</span><br>
<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
<br>
<span style=3D"font-family: Tahoma, sans-serif; ">Topic: IETF CDNI Logging =
- Informal Meeting&nbsp;<br>
<b><span style=3D"color: rgb(145, 38, 4); ">Date: Wednesday, June 26, 2013&=
nbsp;</span></b><br>
Time: 5:00 pm, Europe Summer Time (Paris, GMT&#43;02:00)&nbsp;<br>
Meeting Number: 208 330 914&nbsp;<br>
Password: cdni&nbsp;<br>
<br>
-------------------------------------------------------&nbsp;<br>
To join the meeting online(Now from mobile devices!)&nbsp;<br>
-------------------------------------------------------&nbsp;<br>
1. Go to&nbsp;</span><a href=3D"https://cisco.webex.com/ciscosales/j.php?ED=
=3D225213802&amp;UID=3D484318167&amp;PW=3DNNzQ0ZmZmNjUz&amp;RT=3DMiMyMw%3D%=
3D" target=3D"_blank" style=3D"color: purple; text-decoration: underline; "=
><span style=3D"font-family: Tahoma, sans-serif; ">https://cisco.webex.com/=
ciscosales/j.php?ED=3D225213802&amp;UID=3D484318167&amp;PW=3DNNzQ0ZmZmNjUz&=
amp;RT=3DMiMyMw%3D%3D</span></a><span style=3D"font-family: Tahoma, sans-se=
rif; ">&nbsp;<br>
2. If requested, enter your name and email address.&nbsp;<br>
3. If a password is required, enter the meeting password: cdni&nbsp;<br>
4. Click &quot;Join&quot;.&nbsp;<br>
5. If the meeting includes a teleconference, follow the instructions that a=
ppear on your screen.&nbsp;<br>
<br>
-------------------------------------------------------&nbsp;<br>
To join the audio conference only&nbsp;<br>
-------------------------------------------------------&nbsp;<br>
To receive a call back, provide your phone number when you join the meeting=
, or call the number below and enter the access code.&nbsp;<br>
Call-in toll-free number (US/Canada): &#43;1-866-432-9903&nbsp;<br>
Call-in toll number (US/Canada): &#43;1-408-525-6800&nbsp;<br>
Toll-free dialing restrictions:&nbsp;</span><a href=3D"http://www.webex.com=
/pdf/tollfree_restrictions.pdf" target=3D"_blank" style=3D"color: purple; t=
ext-decoration: underline; "><span style=3D"font-family: Tahoma, sans-serif=
; ">http://www.webex.com/pdf/tollfree_restrictions.pdf</span></a><span styl=
e=3D"font-family: Tahoma, sans-serif; ">&nbsp;<br>
<br>
Access code:208 330 914&nbsp;<br>
<br>
CCP:&#43;14085256800x208330914#&nbsp;<br>
</span><br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<span style=3D"font-family: Tahoma, =
sans-serif; "><br>
IMPORTANT NOTICE: This WebEx service includes a feature that allows audio a=
nd any documents and other materials exchanged or viewed during the session=
 to be recorded. By joining this session, you automatically consent to such=
 recordings. If you do not consent
 to the recording, discuss your concerns with the meeting host prior to the=
 start of the recording or do not join the session. Please note that any su=
ch recordings may be subject to discovery in the event of litigation.&nbsp;=
</span><o:p></o:p></div>
</div>
</div>
<pre>______________________________________________________________________=
___________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for message=
s that have been modified, changed or falsified.
Thank you.
</pre>
</div>
</blockquote>
</div>
<br>
</body>
</html>

--_000_FC236DA6F2DA77449EF2D02DF4471A8D60161Exmbrcdx10ciscocom_--

From kleung@cisco.com  Tue May 14 13:15:30 2013
Return-Path: <kleung@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 2E1DE21F86BB for <cdni@ietfa.amsl.com>; Tue, 14 May 2013 13:15:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 FvPrvSVGwBT6 for <cdni@ietfa.amsl.com>; Tue, 14 May 2013 13:15:25 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id B645A21F85D1 for <cdni@ietf.org>; Tue, 14 May 2013 13:15:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12675; q=dns/txt; s=iport; t=1368562524; x=1369772124; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=7AuLJBppDAGoWmgDo0hNzxO9k37WdDOAStmnmcO0HCc=; b=g+R1qEdRpSUpAG6Z4IawlDKfgcW3HQSCUP8GjVCP2CqtrLceahmrUpEj nAW0gj4dBC/5TRINJNSVjxnkz/WTtcYJkYdiH7q6Hb+JtrYLpMdeMjL0f JiL3bnhW/+uXr2LOMQwPguo8mjKr8c3EoTxg4nQrdAa1w7Sn/oBVLFXol s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhUFAIeaklGtJV2a/2dsb2JhbABagkNEN0S/Z4ECFnSCHwEBAQQBAQEqQRsCAQgRAwEBAQsdBycLFAkIAgQBEggBiAIBBwWuYo8ljVyBESANCgEGgm5hA6hxgw+BcjU
X-IronPort-AV: E=Sophos;i="4.87,672,1363132800";  d="scan'208,217";a="210259469"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-1.cisco.com with ESMTP; 14 May 2013 20:15:24 +0000
Received: from xhc-aln-x02.cisco.com (xhc-aln-x02.cisco.com [173.36.12.76]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r4EKFNHO012300 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <cdni@ietf.org>; Tue, 14 May 2013 20:15:23 GMT
Received: from xmb-aln-x03.cisco.com ([169.254.6.159]) by xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.02.0318.004; Tue, 14 May 2013 15:15:23 -0500
From: "Kent Leung (kleung)" <kleung@cisco.com>
To: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>, "cdni@ietf.org" <cdni@ietf.org>
Thread-Topic: [CDNi] WG Last Call on draft-ietf-cdni-requirements-06.txt
Thread-Index: AQHONtVcTTK3EhU+h0KHYCH7+69QVJjtLdUAgBgjp1A=
Date: Tue, 14 May 2013 20:15:22 +0000
Message-ID: <CD85F32117029D4F9AEF48BDEF5536AB10253877@xmb-aln-x03.cisco.com>
References: <20130409175254.29406.52063.idtracker@ietfa.amsl.com> <FC236DA6F2DA77449EF2D02DF4471A8D3E6AC5@xmb-rcd-x10.cisco.com> <FC236DA6F2DA77449EF2D02DF4471A8D4197C8@xmb-rcd-x10.cisco.com>
In-Reply-To: <FC236DA6F2DA77449EF2D02DF4471A8D4197C8@xmb-rcd-x10.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [171.69.41.43]
Content-Type: multipart/alternative; boundary="_000_CD85F32117029D4F9AEF48BDEF5536AB10253877xmbalnx03ciscoc_"
MIME-Version: 1.0
Subject: Re: [CDNi] WG Last Call on draft-ietf-cdni-requirements-06.txt
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: Tue, 14 May 2013 20:15:30 -0000

--_000_CD85F32117029D4F9AEF48BDEF5536AB10253877xmbalnx03ciscoc_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Since there were no changes needed during WGLC, should I publish a new vers=
ion with the following change?

"I just noticed an editorial nit for MI-21. That will be fixed for review c=
omments during WGLC."

Kent

From: cdni-bounces@ietf.org [mailto:cdni-bounces@ietf.org] On Behalf Of Fra=
ncois Le Faucheur (flefauch)
Sent: Sunday, April 28, 2013 11:36 PM
To: cdni@ietf.org
Subject: Re: [CDNi] WG Last Call on draft-ietf-cdni-requirements-06.txt

Hello,

This closes the WG Last Call on draft-ietf-cdni-requirements-06.txt.
We'll move the document forward.

Cheers

Francois & Daryl

On 11 Apr 2013, at 18:55, Francois Le Faucheur (flefauch) <flefauch@cisco.c=
om<mailto:flefauch@cisco.com>> wrote:


Folks,

This email initiates a CDNI WG Last Call on:

http://www.ietf.org/internet-drafts/draft-ietf-cdni-requirements-06.txt


Please comment on the list on this document in view of publishing it as a S=
tandards Track RFC from the CDNI WG.

This Last Call will close on Friday April 26th.

Francois & Daryl


Begin forwarded message:


Resent-From: <wg-alias-bounces@tools.ietf.org<mailto:wg-alias-bounces@tools=
.ietf.org>>
From: <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>>
Subject: New Version Notification - draft-ietf-cdni-requirements-06.txt
Date: 9 April 2013 19:52:54 CEST
Resent-To: <kleung@cisco.com<mailto:kleung@cisco.com>>, <yiu_lee@cable.comc=
ast.com<mailto:yiu_lee@cable.comcast.com>>, <d.malas@cablelabs.com<mailto:d=
.malas@cablelabs.com>>, <flefauch@cisco.com<mailto:flefauch@cisco.com>>
To: <cdni-chairs@tools.ietf.org<mailto:cdni-chairs@tools.ietf.org>>, <draft=
-ietf-cdni-requirements@tools.ietf.org<mailto:draft-ietf-cdni-requirements@=
tools.ietf.org>>, <martin.stiemerling@neclab.eu<mailto:martin.stiemerling@n=
eclab.eu>>


A new version (-06) has been submitted for draft-ietf-cdni-requirements:
http://www.ietf.org/internet-drafts/draft-ietf-cdni-requirements-06.txt


The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-cdni-requirements/

Diff from previous version:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cdni-requirements-06

IETF Secretariat.

_______________________________________________
CDNi mailing list
CDNi@ietf.org<mailto:CDNi@ietf.org>
https://www.ietf.org/mailman/listinfo/cdni


--_000_CD85F32117029D4F9AEF48BDEF5536AB10253877xmbalnx03ciscoc_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Since there were no chang=
es needed during WGLC, should I publish a new version with the following ch=
ange?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal" style=3D"text-indent:.5in"><span style=3D"font-size:=
11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D=
">&#8220;I just noticed an editorial nit for MI-21. That will be fixed for =
review comments during WGLC.&#8221;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Kent<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> cdni-bou=
nces@ietf.org [mailto:cdni-bounces@ietf.org]
<b>On Behalf Of </b>Francois Le Faucheur (flefauch)<br>
<b>Sent:</b> Sunday, April 28, 2013 11:36 PM<br>
<b>To:</b> cdni@ietf.org<br>
<b>Subject:</b> Re: [CDNi] WG Last Call on draft-ietf-cdni-requirements-06.=
txt<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hello, <o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">This closes the WG Last Call&nbsp;on draft-ietf-cdni=
-requirements-06.txt.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">We'll move the document forward.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Cheers<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Francois &amp; Daryl<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal">On 11 Apr 2013, at 18:55, Francois Le Faucheur (flef=
auch) &lt;<a href=3D"mailto:flefauch@cisco.com">flefauch@cisco.com</a>&gt; =
wrote:<o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><br>
<br>
<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">Folks, <o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">This email initiates a CDNI WG Last Call on:<o:p></o=
:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><a href=3D"http://www.ietf.org/internet-drafts/draft=
-ietf-cdni-requirements-06.txt">http://www.ietf.org/internet-drafts/draft-i=
etf-cdni-requirements-06.txt</a><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Please comment on the list on this document in view =
of publishing it&nbsp;as a Standards Track RFC from the CDNI WG.<o:p></o:p>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">This Last Call will close on Friday April 26th.<o:p>=
</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Francois &amp; Daryl<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">Begin forwarded message:<o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><br>
<br>
<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><b><span style=3D"font-size:13.5pt;font-family:&quot=
;Helvetica&quot;,&quot;sans-serif&quot;">Resent-From:
</span></b><span style=3D"font-size:13.5pt;font-family:&quot;Helvetica&quot=
;,&quot;sans-serif&quot;">&lt;<a href=3D"mailto:wg-alias-bounces@tools.ietf=
.org">wg-alias-bounces@tools.ietf.org</a>&gt;</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><b><span style=3D"font-size:13.5pt;font-family:&quot=
;Helvetica&quot;,&quot;sans-serif&quot;">From:
</span></b><span style=3D"font-size:13.5pt;font-family:&quot;Helvetica&quot=
;,&quot;sans-serif&quot;">&lt;<a href=3D"mailto:internet-drafts@ietf.org">i=
nternet-drafts@ietf.org</a>&gt;</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><b><span style=3D"font-size:13.5pt;font-family:&quot=
;Helvetica&quot;,&quot;sans-serif&quot;">Subject: New Version Notification =
- draft-ietf-cdni-requirements-06.txt</span></b><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><b><span style=3D"font-size:13.5pt;font-family:&quot=
;Helvetica&quot;,&quot;sans-serif&quot;">Date:
</span></b><span style=3D"font-size:13.5pt;font-family:&quot;Helvetica&quot=
;,&quot;sans-serif&quot;">9 April 2013 19:52:54 CEST</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><b><span style=3D"font-size:13.5pt;font-family:&quot=
;Helvetica&quot;,&quot;sans-serif&quot;">Resent-To:
</span></b><span style=3D"font-size:13.5pt;font-family:&quot;Helvetica&quot=
;,&quot;sans-serif&quot;">&lt;<a href=3D"mailto:kleung@cisco.com">kleung@ci=
sco.com</a>&gt;, &lt;<a href=3D"mailto:yiu_lee@cable.comcast.com">yiu_lee@c=
able.comcast.com</a>&gt;, &lt;<a href=3D"mailto:d.malas@cablelabs.com">d.ma=
las@cablelabs.com</a>&gt;,
 &lt;<a href=3D"mailto:flefauch@cisco.com">flefauch@cisco.com</a>&gt;</span=
><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><b><span style=3D"font-size:13.5pt;font-family:&quot=
;Helvetica&quot;,&quot;sans-serif&quot;">To:
</span></b><span style=3D"font-size:13.5pt;font-family:&quot;Helvetica&quot=
;,&quot;sans-serif&quot;">&lt;<a href=3D"mailto:cdni-chairs@tools.ietf.org"=
>cdni-chairs@tools.ietf.org</a>&gt;, &lt;<a href=3D"mailto:draft-ietf-cdni-=
requirements@tools.ietf.org">draft-ietf-cdni-requirements@tools.ietf.org</a=
>&gt;,
 &lt;<a href=3D"mailto:martin.stiemerling@neclab.eu">martin.stiemerling@nec=
lab.eu</a>&gt;</span><o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
A new version (-06) has been submitted for draft-ietf-cdni-requirements:<br=
>
<a href=3D"http://www.ietf.org/internet-drafts/draft-ietf-cdni-requirements=
-06.txt">http://www.ietf.org/internet-drafts/draft-ietf-cdni-requirements-0=
6.txt</a><br>
<br>
<br>
The IETF datatracker page for this Internet-Draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-cdni-requirements/">=
https://datatracker.ietf.org/doc/draft-ietf-cdni-requirements/</a><br>
<br>
Diff from previous version:<br>
<a href=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cdni-requirements-=
06">http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cdni-requirements-06</a><=
br>
<br>
IETF Secretariat.<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
<p class=3D"MsoNormal">_______________________________________________<br>
CDNi mailing list<br>
<a href=3D"mailto:CDNi@ietf.org">CDNi@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/cdni">https://www.ietf.org=
/mailman/listinfo/cdni</a><o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_CD85F32117029D4F9AEF48BDEF5536AB10253877xmbalnx03ciscoc_--

From ray.vanbrandenburg@tno.nl  Fri May 17 08:18:42 2013
Return-Path: <ray.vanbrandenburg@tno.nl>
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 C7E0821F870F for <cdni@ietfa.amsl.com>; Fri, 17 May 2013 08:18:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.503
X-Spam-Level: 
X-Spam-Status: No, score=-0.503 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, HTML_MESSAGE=0.001]
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 kRSTutQYnX9v for <cdni@ietfa.amsl.com>; Fri, 17 May 2013 08:18:38 -0700 (PDT)
Received: from fromintoutb.tno.nl (fromintoutb.tno.nl [134.221.1.27]) by ietfa.amsl.com (Postfix) with ESMTP id C37AE21F871C for <cdni@ietf.org>; Fri, 17 May 2013 08:18:37 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,693,1363129200"; d="scan'208,217";a="1436929"
Received: from unknown (HELO mail.tno.nl) ([134.221.225.221]) by mailhost1b.tno.nl with ESMTP; 17 May 2013 17:18:36 +0200
Received: from EXC-MBX03.tsn.tno.nl ([169.254.3.30]) by EXC-CASHUB02.tsn.tno.nl ([134.221.225.221]) with mapi id 14.02.0318.004; Fri, 17 May 2013 17:18:36 +0200
From: "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl>
To: "cdni@ietf.org" <cdni@ietf.org>
Thread-Topic: Joint MPEG workshop on impact of DASH on network infrastructure 
Thread-Index: Ac5TEc0PNR0nLLTATWSTd2Rak5OqOw==
Date: Fri, 17 May 2013 15:18:36 +0000
Message-ID: <C14E1C4E-372B-47BB-A45C-BC794AB0A246@tno.nl>
Accept-Language: en-US, nl-NL
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_C14E1C4E372B47BBA45CBC794AB0A246tnonl_"
MIME-Version: 1.0
Subject: [CDNi] Joint MPEG workshop on impact of DASH on network infrastructure
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, 17 May 2013 15:18:42 -0000

--_000_C14E1C4E372B47BBA45CBC794AB0A246tnonl_
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64

SGkgYWxsLA0KDQpUaGUgZGF5IGJlZm9yZSB0aGUgQmVybGluIG1lZXRpbmcgKEp1bHkgMjh0aCks
IE1QRUcgd2lsbCBvcmdhbml6ZSB0aGUgZm9sbG93aW5nIG1lZXRpbmc6IE1QRUcgV29ya3Nob3Ag
b24gU2Vzc2lvbiBNYW5hZ2VtZW50IGFuZCBDb250cm9sIGZvciBNUEVHIER5bmFtaWMgQWRhcHRp
dmUgU3RyZWFtaW5nIG92ZXIgSFRUUCAoREFTSCkuDQoNClRoZSBpZGVhIG9mIHRoZSB3b3Jrc2hv
cCBpcyB0byBicmluZyB0b2dldGhlciBleHBlcnRzIGZyb20gdmFyaW91cyBzdGFuZGFyZGl6YXRp
b24gb3JnYW5pemF0aW9ucyAoSUVURiwgTVBFRywgVzNDLCAzR1BQLCBldGMuKSwgbmV0d29yayBv
cGVyYXRvcnMsIGFuZCAob3Zlci10aGUtdG9wKSBzZXJ2aWNlIHByb3ZpZGVycyB0byBkaXNjdXNz
IHRoZSBkZWxpdmVyeSBhc3BlY3RzIG9mIERBU0ggYW5kIGhvdyB0byBlbmhhbmNlIHRoZW0gd2l0
aCB0aGUgZXhpc3Rpbmcgc3RhbmRhcmRzLg0KDQpPbmUgb2YgdGhlIHRvcGljcyBvbiB0aGUgYWdl
bmRhIGlzIHRoZSBpbXBhY3Qgb2YgREFTSCBvbiBDRE5zLiBTaW5jZSB0aGUgbWVldGluZyBpcyBp
biBWaWVubmEgKHdoaWNoIGlzIG5vdCB0aGF0IGZhciBmcm9tIEJlcmxpbiksIGl0IG1pZ2h0IGJl
IHNvbWV0aGluZyB0aGF0IHNvbWUgb2YgeW91IGFyZSBpbnRlcmVzdGVkIGluLiBFc3BlY2lhbGx5
IHNpbmNlIHdlIGFsbCBrbm93IHRoYXQgREFTSCBhbmQgb3RoZXIgSEFTLXRlY2hub2xvZ2llcyBh
bHNvIGhhdmUgYW4gZWZmZWN0IG9uIENETkkuDQoNClNlZSBiZWxvdyBmb3IgbW9yZSBpbmZvOg0K
aHR0cDovL211bHRpbWVkaWFjb21tdW5pY2F0aW9uLmJsb2dzcG90Lm5sLzIwMTMvMDUvbXBlZy13
b3Jrc2hvcC1vbi1zZXNzaW9uLW1hbmFnZW1lbnQtYW5kLmh0bWw/bT0xDQoNCkJlc3QgcmVnYXJk
cywNCg0KUmF5DQoNCg0KVGhpcyBlLW1haWwgYW5kIGl0cyBjb250ZW50cyBhcmUgc3ViamVjdCB0
byB0aGUgRElTQ0xBSU1FUiBhdCBodHRwOi8vd3d3LnRuby5ubC9lbWFpbGRpc2NsYWltZXIK

--_000_C14E1C4E372B47BBA45CBC794AB0A246tnonl_
Content-Type: text/html; charset="utf-8"
Content-ID: <0A35D76CF3DEF7469F41C9623A69A667@tno.nl>
MIME-Version: 1.0
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IGRpcj0iYXV0byI+DQo8
ZGl2PjxzcGFuPjwvc3Bhbj48L2Rpdj4NCjxkaXY+PHNwYW4gc3R5bGU9Ii13ZWJraXQtdGV4dC1z
aXplLWFkanVzdDogYXV0bzsiPkhpIGFsbCw8L3NwYW4+DQo8ZGl2IHN0eWxlPSItd2Via2l0LXRl
eHQtc2l6ZS1hZGp1c3Q6IGF1dG87ICI+PGJyPg0KPC9kaXY+DQo8ZGl2IHN0eWxlPSItd2Via2l0
LXRleHQtc2l6ZS1hZGp1c3Q6IGF1dG87ICI+VGhlIGRheSBiZWZvcmUgdGhlIEJlcmxpbiBtZWV0
aW5nIChKdWx5IDI4dGgpLCBNUEVHIHdpbGwgb3JnYW5pemUgdGhlIGZvbGxvd2luZyBtZWV0aW5n
OiZuYnNwOzxzcGFuIHN0eWxlPSJiYWNrZ3JvdW5kLWNvbG9yOiByZ2JhKDI1NSwgMjU1LCAyNTUs
IDApOyAiPk1QRUcgV29ya3Nob3Agb24gU2Vzc2lvbiBNYW5hZ2VtZW50IGFuZCBDb250cm9sIGZv
ciBNUEVHIER5bmFtaWMNCiBBZGFwdGl2ZSBTdHJlYW1pbmcgb3ZlciBIVFRQIChEQVNIKS4mbmJz
cDs8L3NwYW4+PC9kaXY+DQo8ZGl2IHN0eWxlPSItd2Via2l0LXRleHQtc2l6ZS1hZGp1c3Q6IGF1
dG87ICI+PHNwYW4gc3R5bGU9ImJhY2tncm91bmQtY29sb3I6IHJnYmEoMjU1LCAyNTUsIDI1NSwg
MCk7ICI+PGJyPg0KPC9zcGFuPjwvZGl2Pg0KPGRpdj48c3BhbiBzdHlsZT0iLXdlYmtpdC10ZXh0
LXNpemUtYWRqdXN0OiBhdXRvOyBiYWNrZ3JvdW5kLWNvbG9yOiByZ2JhKDI1NSwgMjU1LCAyNTUs
IDApOyAiPlRoZSBpZGVhIG9mIHRoZSB3b3Jrc2hvcCBpcyB0byZuYnNwOzwvc3Bhbj48c3BhbiBz
dHlsZT0idGV4dC1hbGlnbjogbGVmdDsgYmFja2dyb3VuZC1jb2xvcjogcmdiYSgyNTUsIDI1NSwg
MjU1LCAwKTsiPmJyaW5nIHRvZ2V0aGVyIGV4cGVydHMgZnJvbSB2YXJpb3VzIHN0YW5kYXJkaXph
dGlvbg0KIG9yZ2FuaXphdGlvbnMgKElFVEYsIE1QRUcsIFczQywgM0dQUCwgZXRjLiksIG5ldHdv
cmsgb3BlcmF0b3JzLCBhbmQgKG92ZXItdGhlLXRvcCkgc2VydmljZSBwcm92aWRlcnMgdG8gZGlz
Y3VzcyB0aGUgZGVsaXZlcnkgYXNwZWN0cyBvZiBEQVNIIGFuZCBob3cgdG8gZW5oYW5jZSB0aGVt
IHdpdGggdGhlIGV4aXN0aW5nIHN0YW5kYXJkcy48L3NwYW4+PC9kaXY+DQo8ZGl2PjxzcGFuIHN0
eWxlPSJ0ZXh0LWFsaWduOiBsZWZ0OyBiYWNrZ3JvdW5kLWNvbG9yOiByZ2JhKDI1NSwgMjU1LCAy
NTUsIDApOyI+PGJyPg0KPC9zcGFuPjwvZGl2Pg0KPGRpdiBzdHlsZT0idGV4dC1hbGlnbjogbGVm
dDsiPk9uZSBvZiB0aGUgdG9waWNzIG9uIHRoZSBhZ2VuZGEgaXMgdGhlIGltcGFjdCBvZiBEQVNI
IG9uIENETnMuJm5ic3A7U2luY2UgdGhlIG1lZXRpbmcgaXMgaW4gVmllbm5hICh3aGljaCBpcyBu
b3QgdGhhdCBmYXIgZnJvbSBCZXJsaW4pLCBpdCBtaWdodCBiZSBzb21ldGhpbmcgdGhhdCBzb21l
IG9mIHlvdSBhcmUgaW50ZXJlc3RlZCBpbi4gRXNwZWNpYWxseSBzaW5jZSB3ZSBhbGwga25vdyB0
aGF0IERBU0gNCiBhbmQgb3RoZXIgSEFTLXRlY2hub2xvZ2llcyBhbHNvIGhhdmUgYW4gZWZmZWN0
IG9uIENETkkuPC9kaXY+DQo8ZGl2IHN0eWxlPSJ0ZXh0LWFsaWduOiBsZWZ0OyI+PGJyPg0KPC9k
aXY+DQo8ZGl2IHN0eWxlPSJ0ZXh0LWFsaWduOiBsZWZ0OyI+U2VlIGJlbG93IGZvciBtb3JlIGlu
Zm86PC9kaXY+DQo8ZGl2IHN0eWxlPSJ0ZXh0LWFsaWduOiBsZWZ0OyI+PHNwYW4gc3R5bGU9ImZv
bnQtZmFtaWx5OiAnLkhlbHZldGljYU5ldWVVSSc7IGZvbnQtc2l6ZTogMTVweDsgbGluZS1oZWln
aHQ6IDE5cHg7IHRleHQtYWxpZ246IC13ZWJraXQtYXV0bzsgd2hpdGUtc3BhY2U6IG5vd3JhcDsg
LXdlYmtpdC10YXAtaGlnaGxpZ2h0LWNvbG9yOiByZ2JhKDI2LCAyNiwgMjYsIDAuMjk2ODc1KTsg
LXdlYmtpdC1jb21wb3NpdGlvbi1maWxsLWNvbG9yOiByZ2JhKDE3NSwgMTkyLCAyMjcsIDAuMjMw
NDY5KTsgLXdlYmtpdC1jb21wb3NpdGlvbi1mcmFtZS1jb2xvcjogcmdiYSg3NywgMTI4LCAxODAs
IDAuMjMwNDY5KTsgIj48YSBocmVmPSJodHRwOi8vbXVsdGltZWRpYWNvbW11bmljYXRpb24uYmxv
Z3Nwb3QubmwvMjAxMy8wNS9tcGVnLXdvcmtzaG9wLW9uLXNlc3Npb24tbWFuYWdlbWVudC1hbmQu
aHRtbD9tPTEiPmh0dHA6Ly9tdWx0aW1lZGlhY29tbXVuaWNhdGlvbi5ibG9nc3BvdC5ubC8yMDEz
LzA1L21wZWctd29ya3Nob3Atb24tc2Vzc2lvbi1tYW5hZ2VtZW50LWFuZC5odG1sP209MTwvYT48
L3NwYW4+PC9kaXY+DQo8ZGl2IHN0eWxlPSJ0ZXh0LWFsaWduOiBsZWZ0OyI+PHNwYW4gc3R5bGU9
ImZvbnQtZmFtaWx5OiAnLkhlbHZldGljYU5ldWVVSSc7IGZvbnQtc2l6ZTogMTVweDsgbGluZS1o
ZWlnaHQ6IDE5cHg7IHRleHQtYWxpZ246IC13ZWJraXQtYXV0bzsgd2hpdGUtc3BhY2U6IG5vd3Jh
cDsgLXdlYmtpdC10YXAtaGlnaGxpZ2h0LWNvbG9yOiByZ2JhKDI2LCAyNiwgMjYsIDAuMjk2ODc1
KTsgLXdlYmtpdC1jb21wb3NpdGlvbi1maWxsLWNvbG9yOiByZ2JhKDE3NSwgMTkyLCAyMjcsIDAu
MjMwNDY5KTsgLXdlYmtpdC1jb21wb3NpdGlvbi1mcmFtZS1jb2xvcjogcmdiYSg3NywgMTI4LCAx
ODAsIDAuMjMwNDY5KTsgIj48YnI+DQo8L3NwYW4+PC9kaXY+DQo8ZGl2IHN0eWxlPSJ0ZXh0LWFs
aWduOiBsZWZ0OyI+PHNwYW4gc3R5bGU9Ii13ZWJraXQtdGFwLWhpZ2hsaWdodC1jb2xvcjogcmdi
YSgyNiwgMjYsIDI2LCAwLjI5Njg3NSk7IC13ZWJraXQtY29tcG9zaXRpb24tZmlsbC1jb2xvcjog
cmdiYSgxNzUsIDE5MiwgMjI3LCAwLjIzMDQ2OSk7IC13ZWJraXQtY29tcG9zaXRpb24tZnJhbWUt
Y29sb3I6IHJnYmEoNzcsIDEyOCwgMTgwLCAwLjIzMDQ2OSk7ICI+QmVzdCByZWdhcmRzLDwvc3Bh
bj48L2Rpdj4NCjxkaXYgc3R5bGU9InRleHQtYWxpZ246IGxlZnQ7Ij48c3BhbiBzdHlsZT0iLXdl
YmtpdC10YXAtaGlnaGxpZ2h0LWNvbG9yOiByZ2JhKDI2LCAyNiwgMjYsIDAuMjk2ODc1KTsgLXdl
YmtpdC1jb21wb3NpdGlvbi1maWxsLWNvbG9yOiByZ2JhKDE3NSwgMTkyLCAyMjcsIDAuMjMwNDY5
KTsgLXdlYmtpdC1jb21wb3NpdGlvbi1mcmFtZS1jb2xvcjogcmdiYSg3NywgMTI4LCAxODAsIDAu
MjMwNDY5KTsgIj48YnI+DQo8L3NwYW4+PC9kaXY+DQo8ZGl2IHN0eWxlPSJ0ZXh0LWFsaWduOiBs
ZWZ0OyI+PHNwYW4gc3R5bGU9Ii13ZWJraXQtdGFwLWhpZ2hsaWdodC1jb2xvcjogcmdiYSgyNiwg
MjYsIDI2LCAwLjI5Mjk2OSk7IC13ZWJraXQtY29tcG9zaXRpb24tZmlsbC1jb2xvcjogcmdiYSgx
NzUsIDE5MiwgMjI3LCAwLjIzMDQ2OSk7IC13ZWJraXQtY29tcG9zaXRpb24tZnJhbWUtY29sb3I6
IHJnYmEoNzcsIDEyOCwgMTgwLCAwLjIzMDQ2OSk7Ij5SYXk8L3NwYW4+PC9kaXY+DQo8ZGl2IHN0
eWxlPSJ0ZXh0LWFsaWduOiBsZWZ0OyI+PGJyPg0KPC9kaXY+DQo8ZGl2IHN0eWxlPSJ0ZXh0LWFs
aWduOiBsZWZ0OyI+PGJyPg0KPC9kaXY+DQo8L2Rpdj4NCjxwPlRoaXMgZS1tYWlsIGFuZCBpdHMg
Y29udGVudHMgYXJlIHN1YmplY3QgdG8gdGhlIERJU0NMQUlNRVIgYXQgaHR0cDovL3d3dy50bm8u
bmwvZW1haWxkaXNjbGFpbWVyPC9wPjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_C14E1C4E372B47BBA45CBC794AB0A246tnonl_--


From flefauch@cisco.com  Thu May 23 14:51:43 2013
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 EE43E21F9814 for <cdni@ietfa.amsl.com>; Thu, 23 May 2013 14:51:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.998
X-Spam-Level: 
X-Spam-Status: No, score=-9.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_63=0.6, 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 cpPXMNAi0MF0 for <cdni@ietfa.amsl.com>; Thu, 23 May 2013 14:51:28 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id DFA5A21F98AC for <cdni@ietf.org>; Thu, 23 May 2013 14:03:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=26550; q=dns/txt; s=iport; t=1369342983; x=1370552583; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=tx2vwJHKqkDzUzDRiy/JrdiDnO3Sk9MZuwrEOXNZKCM=; b=QTgtuYi9GzpyN0kUoM7UCw6HIPh1IFIxzgyfgEsJXM97Vq9sGxnHiTFU YMOnq1XpGFhE/AmSZCBjPHttphh3nDrdYWaaHtmtfdcgAGQisCAJvrqdv /z/s/vCritQ3qHpOc+PqjGw9Nr4oWFSmQWNh8ongkQHGsBY7Y+dtNoCOB E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvMGAJ2DnlGtJV2Z/2dsb2JhbAA/FwOCREQwwi+BDBZtB4IkAQECAgEBAWMCBhsCAQgUDgoECAQDBycLFBABAgEDEwiIBQwzrBCNNo1bG3YgAQsBCgERB4JbYQOoe4I/UIFxNQ
X-IronPort-AV: E=Sophos;i="4.87,730,1363132800";  d="scan'208,217";a="214349886"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-3.cisco.com with ESMTP; 23 May 2013 21:02:46 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r4NL2jlf022408 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <cdni@ietf.org>; Thu, 23 May 2013 21:02:45 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.56]) by xhc-rcd-x04.cisco.com ([fe80::200:5efe:173.37.183.34%12]) with mapi id 14.02.0318.004; Thu, 23 May 2013 16:02:45 -0500
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "cdni@ietf.org" <cdni@ietf.org>
Thread-Topic: [CDNi] CDNI Logging - Series of Informal Meetings
Thread-Index: AQHOSinCyYxSJinUj0azs1JHewNx8Jj34h8QgABXo4CAG3d4gA==
Date: Thu, 23 May 2013 21:02:44 +0000
Message-ID: <FC236DA6F2DA77449EF2D02DF4471A8D625E00@xmb-rcd-x10.cisco.com>
References: <FC236DA6F2DA77449EF2D02DF4471A8D600780@xmb-rcd-x10.cisco.com> <32176_1367832523_518777CB_32176_694_1_5AE9CCAA1B4A2248AB61B4C7F0AD5FB906C34DC6@PEXCVZYM14.corporate.adroot.infra.ftgroup> <FC236DA6F2DA77449EF2D02DF4471A8D60161E@xmb-rcd-x10.cisco.com>
In-Reply-To: <FC236DA6F2DA77449EF2D02DF4471A8D60161E@xmb-rcd-x10.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.55.161.201]
Content-Type: multipart/alternative; boundary="_000_FC236DA6F2DA77449EF2D02DF4471A8D625E00xmbrcdx10ciscocom_"
MIME-Version: 1.0
Subject: Re: [CDNi] CDNI Logging - Series of Informal Meetings
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: Thu, 23 May 2013 21:51:44 -0000

--_000_FC236DA6F2DA77449EF2D02DF4471A8D625E00xmbrcdx10ciscocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Friendly reminder: first informal meeting on cdni-logging is next Wed.
Cheers
Francois


On 6 May 2013, at 11:36, Francois Le Faucheur (flefauch) <flefauch@cisco.co=
m<mailto:flefauch@cisco.com>> wrote:

Oops =85 correcting the typo pointed out by Emile in the last date:

These informal meetings will be run as Webex sessions on:
* Wed 29 May 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, fo=
r 90 minutes
* Wed 5 June 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, fo=
r 90 minutes
* Wed 26 June 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, f=
or 90 minutes

Francois

On 6 May 2013, at 11:28, emile.stephan@orange.com<mailto:emile.stephan@oran=
ge.com> wrote:

Hi Francois,

Just in case, is the third meeting planned for the 26 of June?

Regards
Emile

De : cdni-bounces@ietf.org<mailto:cdni-bounces@ietf.org> [mailto:cdni-bounc=
es@ietf.org<mailto:bounces@ietf.org>] De la part de Francois Le Faucheur (f=
lefauch)
Envoy=E9 : lundi 6 mai 2013 09:17
=C0 : cdni@ietf.org<mailto:cdni@ietf.org>
Objet : [CDNi] CDNI Logging - Series of Informal Meetings

Hi everyone,

(speaking as one of the cdni-logging co-authors)

We're in the process of revving up cdni-logging to reflect the Orlando disc=
ussions/conclusions. To maximise progress before Berlin, we'll run a series=
 of informal meetings to :
* collect feedback on interim versions of the I-D
* get input on the open items.

These informal meetings will be run as Webex sessions on:
* Wed 29 May 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, fo=
r 90 minutes
* Wed 5 June 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, fo=
r 90 minutes
* Wed 26 May 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, fo=
r 90 minutes

Please try attend and mark these slots in your calendar.

Cheers

Francois & cdni-logging co-authors

PS: Webex details below



=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Topic: IETF CDNI Logging - Informal Meeting
Date: Wednesday, May 29, 2013
Time: 5:00 pm, Europe Summer Time (Paris, GMT+02:00)
Meeting Number: 205 636 967
Password: cdni

-------------------------------------------------------
To join the meeting online(Now from mobile devices!)
-------------------------------------------------------
1. Go to https://cisco.webex.com/ciscosales/j.php?ED=3D225213752&UID=3D4843=
18167&PW=3DNNTMwZTVjNGRk&RT=3DMiMyMw%3D%3D
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: cdni
4. Click "Join".
5. If the meeting includes a teleconference, follow the instructions that a=
ppear on your screen.

-------------------------------------------------------
To join the audio conference only
-------------------------------------------------------
To receive a call back, provide your phone number when you join the meeting=
, or call the number below and enter the access code.
Call-in toll-free number (US/Canada): +1-866-432-9903
Call-in toll number (US/Canada): +1-408-525-6800
Toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restricti=
ons.pdf

Access code:205 636 967

CCP:+14085256800x205636967#

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D


Topic: IETF CDNI Logging - Informal Meeting
Date: Wednesday, June 5, 2013
Time: 5:00 pm, Europe Summer Time (Paris, GMT+02:00)
Meeting Number: 206 470 738
Password: cdni

-------------------------------------------------------
To join the meeting online(Now from mobile devices!)
-------------------------------------------------------
1. Go to https://cisco.webex.com/ciscosales/j.php?ED=3D225213782&UID=3D4843=
18167&PW=3DNMmQzODVmZjJm&RT=3DMiMyMw%3D%3D
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: cdni
4. Click "Join".
5. If the meeting includes a teleconference, follow the instructions that a=
ppear on your screen.

-------------------------------------------------------
To join the audio conference only
-------------------------------------------------------
To receive a call back, provide your phone number when you join the meeting=
, or call the number below and enter the access code.
Call-in toll-free number (US/Canada): +1-866-432-9903
Call-in toll number (US/Canada): +1-408-525-6800
Toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restricti=
ons.pdf

Access code:206 470 738

CCP:+14085256800x206470738#

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Topic: IETF CDNI Logging - Informal Meeting
Date: Wednesday, June 26, 2013
Time: 5:00 pm, Europe Summer Time (Paris, GMT+02:00)
Meeting Number: 208 330 914
Password: cdni

-------------------------------------------------------
To join the meeting online(Now from mobile devices!)
-------------------------------------------------------
1. Go to https://cisco.webex.com/ciscosales/j.php?ED=3D225213802&UID=3D4843=
18167&PW=3DNNzQ0ZmZmNjUz&RT=3DMiMyMw%3D%3D
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: cdni
4. Click "Join".
5. If the meeting includes a teleconference, follow the instructions that a=
ppear on your screen.

-------------------------------------------------------
To join the audio conference only
-------------------------------------------------------
To receive a call back, provide your phone number when you join the meeting=
, or call the number below and enter the access code.
Call-in toll-free number (US/Canada): +1-866-432-9903
Call-in toll number (US/Canada): +1-408-525-6800
Toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restricti=
ons.pdf

Access code:208 330 914

CCP:+14085256800x208330914#

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
IMPORTANT NOTICE: This WebEx service includes a feature that allows audio a=
nd any documents and other materials exchanged or viewed during the session=
 to be recorded. By joining this session, you automatically consent to such=
 recordings. If you do not consent to the recording, discuss your concerns =
with the meeting host prior to the start of the recording or do not join th=
e session. Please note that any such recordings may be subject to discovery=
 in the event of litigation.

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for message=
s that have been modified, changed or falsified.
Thank you.


_______________________________________________
CDNi mailing list
CDNi@ietf.org<mailto:CDNi@ietf.org>
https://www.ietf.org/mailman/listinfo/cdni


--_000_FC236DA6F2DA77449EF2D02DF4471A8D625E00xmbrcdx10ciscocom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <CE8F4027842FFF46BE26FFE0988015A0@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
Friendly reminder: first informal meeting on cdni-logging is next Wed.
<div>Cheers</div>
<div>Francois<br>
<div><br>
</div>
<div><br>
<div>
<div>On 6 May 2013, at 11:36, Francois Le Faucheur (flefauch) &lt;<a href=
=3D"mailto:flefauch@cisco.com">flefauch@cisco.com</a>&gt; wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite"><base href=3D"x-msg://829/">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; ">
<div>Oops =85 correcting the typo pointed out by Emile in the last date:</d=
iv>
<div><br>
</div>
<div>These informal meetings will be run as Webex sessions on:<br>
* Wed 29 May 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, fo=
r 90 minutes<br>
* Wed 5 June 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, fo=
r 90 minutes<br>
* Wed 26 June 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, f=
or 90 minutes</div>
<div><br>
</div>
<div>Francois</div>
<br>
<div>
<div>On 6 May 2013, at 11:28, <a href=3D"mailto:emile.stephan@orange.com">e=
mile.stephan@orange.com</a> wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div lang=3D"FR" link=3D"blue" vlink=3D"purple" style=3D"font-family: Helve=
tica; font-size: medium; font-style: normal; font-variant: normal; font-wei=
ght: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-=
align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: n=
ormal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webki=
t-text-stroke-width: 0px; ">
<div class=3D"WordSection1" style=3D"page: WordSection1; ">
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<span lang=3D"EN-US">Hi Francois,<o:p></o:p></span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<span lang=3D"EN-US">&nbsp;</span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<span lang=3D"EN-US">Just in case, is the third meeting planned for the 26 =
of June?<o:p></o:p></span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<span lang=3D"EN-US" style=3D"font-size: 11pt; font-family: Calibri, sans-s=
erif; color: rgb(31, 73, 125); ">&nbsp;</span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<span lang=3D"EN-US">Regards<o:p></o:p></span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<span lang=3D"EN-US">Emile<o:p></o:p></span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<span lang=3D"EN-US" style=3D"font-size: 11pt; font-family: Calibri, sans-s=
erif; color: rgb(31, 73, 125); ">&nbsp;</span></div>
<div>
<div style=3D"border-style: solid none none; border-top-width: 1pt; border-=
top-color: rgb(181, 196, 223); padding: 3pt 0cm 0cm; ">
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<b><span style=3D"font-size: 10pt; font-family: Tahoma, sans-serif; ">De&nb=
sp;:</span></b><span style=3D"font-size: 10pt; font-family: Tahoma, sans-se=
rif; "><span class=3D"Apple-converted-space">&nbsp;</span><a href=3D"mailto=
:cdni-bounces@ietf.org" style=3D"color: purple; text-decoration: underline;=
 ">cdni-bounces@ietf.org</a><span class=3D"Apple-converted-space">&nbsp;</s=
pan>[mailto:cdni-<a href=3D"mailto:bounces@ietf.org" style=3D"color: purple=
; text-decoration: underline; ">bounces@ietf.org</a>]<span class=3D"Apple-c=
onverted-space">&nbsp;</span><b>De
 la part de</b><span class=3D"Apple-converted-space">&nbsp;</span>Francois =
Le Faucheur (flefauch)<br>
<b>Envoy=E9&nbsp;:</b><span class=3D"Apple-converted-space">&nbsp;</span>lu=
ndi 6 mai 2013 09:17<br>
<b>=C0&nbsp;:</b><span class=3D"Apple-converted-space">&nbsp;</span><a href=
=3D"mailto:cdni@ietf.org" style=3D"color: purple; text-decoration: underlin=
e; ">cdni@ietf.org</a><br>
<b>Objet&nbsp;:</b><span class=3D"Apple-converted-space">&nbsp;</span>[CDNi=
] CDNI Logging - Series of Informal Meetings<o:p></o:p></span></div>
</div>
</div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<o:p>&nbsp;</o:p></div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
Hi everyone,<o:p></o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<o:p>&nbsp;</o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
(speaking as one of the cdni-logging co-authors)<o:p></o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<o:p>&nbsp;</o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
We're in the process of revving up cdni-logging to reflect the Orlando disc=
ussions/conclusions. To maximise progress before Berlin, we'll run&nbsp;a s=
eries of informal meetings to :<o:p></o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
*&nbsp;collect feedback on&nbsp;interim versions of the I-D&nbsp;<o:p></o:p=
></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
* get&nbsp;input on the open items.<o:p></o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<o:p>&nbsp;</o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
These informal meetings will be run as Webex sessions on:<o:p></o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
* Wed 29 May 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, fo=
r 90 minutes<o:p></o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
* Wed 5 June 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, fo=
r 90 minutes<o:p></o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
* Wed 26 May 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, fo=
r 90 minutes<span class=3D"apple-tab-span"><o:p></o:p></span></div>
</div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<o:p></o:p></div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<o:p>&nbsp;</o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
Please try attend and mark these slots in your calendar.<o:p></o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<o:p>&nbsp;</o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
Cheers<o:p></o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<o:p>&nbsp;</o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
Francois &amp; cdni-logging co-authors<o:p></o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<o:p>&nbsp;</o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
PS: Webex details below<o:p></o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<o:p>&nbsp;</o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<o:p>&nbsp;</o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<o:p>&nbsp;</o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
<span style=3D"font-family: Tahoma, sans-serif; "><br>
Topic: IETF CDNI Logging - Informal Meeting&nbsp;<br>
<b><span style=3D"color: rgb(145, 38, 4); ">Date: Wednesday, May 29, 2013&n=
bsp;</span></b><br>
Time: 5:00 pm, Europe Summer Time (Paris, GMT&#43;02:00)&nbsp;<br>
Meeting Number: 205 636 967&nbsp;<br>
Password: cdni&nbsp;<br>
<br>
-------------------------------------------------------&nbsp;<br>
To join the meeting online(Now from mobile devices!)&nbsp;<br>
-------------------------------------------------------&nbsp;<br>
1. Go to&nbsp;</span><a href=3D"https://cisco.webex.com/ciscosales/j.php?ED=
=3D225213752&amp;UID=3D484318167&amp;PW=3DNNTMwZTVjNGRk&amp;RT=3DMiMyMw%3D%=
3D" target=3D"_blank" style=3D"color: purple; text-decoration: underline; "=
><span style=3D"font-family: Tahoma, sans-serif; ">https://cisco.webex.com/=
ciscosales/j.php?ED=3D225213752&amp;UID=3D484318167&amp;PW=3DNNTMwZTVjNGRk&=
amp;RT=3DMiMyMw%3D%3D</span></a><span style=3D"font-family: Tahoma, sans-se=
rif; ">&nbsp;<br>
2. If requested, enter your name and email address.&nbsp;<br>
3. If a password is required, enter the meeting password: cdni&nbsp;<br>
4. Click &quot;Join&quot;.&nbsp;<br>
5. If the meeting includes a teleconference, follow the instructions that a=
ppear on your screen.&nbsp;<br>
<br>
-------------------------------------------------------&nbsp;<br>
To join the audio conference only&nbsp;<br>
-------------------------------------------------------&nbsp;<br>
To receive a call back, provide your phone number when you join the meeting=
, or call the number below and enter the access code.&nbsp;<br>
Call-in toll-free number (US/Canada): &#43;1-866-432-9903&nbsp;<br>
Call-in toll number (US/Canada): &#43;1-408-525-6800&nbsp;<br>
Toll-free dialing restrictions:&nbsp;</span><a href=3D"http://www.webex.com=
/pdf/tollfree_restrictions.pdf" target=3D"_blank" style=3D"color: purple; t=
ext-decoration: underline; "><span style=3D"font-family: Tahoma, sans-serif=
; ">http://www.webex.com/pdf/tollfree_restrictions.pdf</span></a><span styl=
e=3D"font-family: Tahoma, sans-serif; ">&nbsp;<br>
<br>
Access code:205 636 967&nbsp;<br>
<br>
CCP:&#43;14085256800x205636967#&nbsp;<br>
</span><br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D<br>
<br>
<br>
<span style=3D"font-family: Tahoma, sans-serif; ">Topic: IETF CDNI Logging =
- Informal Meeting&nbsp;<br>
<b><span style=3D"color: rgb(145, 38, 4); ">Date: Wednesday, June 5, 2013&n=
bsp;</span></b><br>
Time: 5:00 pm, Europe Summer Time (Paris, GMT&#43;02:00)&nbsp;<br>
Meeting Number: 206 470 738&nbsp;<br>
Password: cdni&nbsp;<br>
<br>
-------------------------------------------------------&nbsp;<br>
To join the meeting online(Now from mobile devices!)&nbsp;<br>
-------------------------------------------------------&nbsp;<br>
1. Go to&nbsp;</span><a href=3D"https://cisco.webex.com/ciscosales/j.php?ED=
=3D225213782&amp;UID=3D484318167&amp;PW=3DNMmQzODVmZjJm&amp;RT=3DMiMyMw%3D%=
3D" target=3D"_blank" style=3D"color: purple; text-decoration: underline; "=
><span style=3D"font-family: Tahoma, sans-serif; ">https://cisco.webex.com/=
ciscosales/j.php?ED=3D225213782&amp;UID=3D484318167&amp;PW=3DNMmQzODVmZjJm&=
amp;RT=3DMiMyMw%3D%3D</span></a><span style=3D"font-family: Tahoma, sans-se=
rif; ">&nbsp;<br>
2. If requested, enter your name and email address.&nbsp;<br>
3. If a password is required, enter the meeting password: cdni&nbsp;<br>
4. Click &quot;Join&quot;.&nbsp;<br>
5. If the meeting includes a teleconference, follow the instructions that a=
ppear on your screen.&nbsp;<br>
<br>
-------------------------------------------------------&nbsp;<br>
To join the audio conference only&nbsp;<br>
-------------------------------------------------------&nbsp;<br>
To receive a call back, provide your phone number when you join the meeting=
, or call the number below and enter the access code.&nbsp;<br>
Call-in toll-free number (US/Canada): &#43;1-866-432-9903&nbsp;<br>
Call-in toll number (US/Canada): &#43;1-408-525-6800&nbsp;<br>
Toll-free dialing restrictions:&nbsp;</span><a href=3D"http://www.webex.com=
/pdf/tollfree_restrictions.pdf" target=3D"_blank" style=3D"color: purple; t=
ext-decoration: underline; "><span style=3D"font-family: Tahoma, sans-serif=
; ">http://www.webex.com/pdf/tollfree_restrictions.pdf</span></a><span styl=
e=3D"font-family: Tahoma, sans-serif; ">&nbsp;<br>
<br>
Access code:206 470 738&nbsp;<br>
<br>
CCP:&#43;14085256800x206470738#&nbsp;</span><br>
<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
<br>
<span style=3D"font-family: Tahoma, sans-serif; ">Topic: IETF CDNI Logging =
- Informal Meeting&nbsp;<br>
<b><span style=3D"color: rgb(145, 38, 4); ">Date: Wednesday, June 26, 2013&=
nbsp;</span></b><br>
Time: 5:00 pm, Europe Summer Time (Paris, GMT&#43;02:00)&nbsp;<br>
Meeting Number: 208 330 914&nbsp;<br>
Password: cdni&nbsp;<br>
<br>
-------------------------------------------------------&nbsp;<br>
To join the meeting online(Now from mobile devices!)&nbsp;<br>
-------------------------------------------------------&nbsp;<br>
1. Go to&nbsp;</span><a href=3D"https://cisco.webex.com/ciscosales/j.php?ED=
=3D225213802&amp;UID=3D484318167&amp;PW=3DNNzQ0ZmZmNjUz&amp;RT=3DMiMyMw%3D%=
3D" target=3D"_blank" style=3D"color: purple; text-decoration: underline; "=
><span style=3D"font-family: Tahoma, sans-serif; ">https://cisco.webex.com/=
ciscosales/j.php?ED=3D225213802&amp;UID=3D484318167&amp;PW=3DNNzQ0ZmZmNjUz&=
amp;RT=3DMiMyMw%3D%3D</span></a><span style=3D"font-family: Tahoma, sans-se=
rif; ">&nbsp;<br>
2. If requested, enter your name and email address.&nbsp;<br>
3. If a password is required, enter the meeting password: cdni&nbsp;<br>
4. Click &quot;Join&quot;.&nbsp;<br>
5. If the meeting includes a teleconference, follow the instructions that a=
ppear on your screen.&nbsp;<br>
<br>
-------------------------------------------------------&nbsp;<br>
To join the audio conference only&nbsp;<br>
-------------------------------------------------------&nbsp;<br>
To receive a call back, provide your phone number when you join the meeting=
, or call the number below and enter the access code.&nbsp;<br>
Call-in toll-free number (US/Canada): &#43;1-866-432-9903&nbsp;<br>
Call-in toll number (US/Canada): &#43;1-408-525-6800&nbsp;<br>
Toll-free dialing restrictions:&nbsp;</span><a href=3D"http://www.webex.com=
/pdf/tollfree_restrictions.pdf" target=3D"_blank" style=3D"color: purple; t=
ext-decoration: underline; "><span style=3D"font-family: Tahoma, sans-serif=
; ">http://www.webex.com/pdf/tollfree_restrictions.pdf</span></a><span styl=
e=3D"font-family: Tahoma, sans-serif; ">&nbsp;<br>
<br>
Access code:208 330 914&nbsp;<br>
<br>
CCP:&#43;14085256800x208330914#&nbsp;<br>
</span><br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<span style=3D"font-family: Tahoma, =
sans-serif; "><br>
IMPORTANT NOTICE: This WebEx service includes a feature that allows audio a=
nd any documents and other materials exchanged or viewed during the session=
 to be recorded. By joining this session, you automatically consent to such=
 recordings. If you do not consent
 to the recording, discuss your concerns with the meeting host prior to the=
 start of the recording or do not join the session. Please note that any su=
ch recordings may be subject to discovery in the event of litigation.&nbsp;=
</span><o:p></o:p></div>
</div>
</div>
<pre>______________________________________________________________________=
___________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for message=
s that have been modified, changed or falsified.
Thank you.
</pre>
</div>
</blockquote>
</div>
<br>
</div>
_______________________________________________<br>
CDNi mailing list<br>
<a href=3D"mailto:CDNi@ietf.org">CDNi@ietf.org</a><br>
https://www.ietf.org/mailman/listinfo/cdni<br>
</blockquote>
</div>
<br>
</div>
</div>
</body>
</html>

--_000_FC236DA6F2DA77449EF2D02DF4471A8D625E00xmbrcdx10ciscocom_--

From D.Malas@cablelabs.com  Fri May 24 13:35:14 2013
Return-Path: <D.Malas@cablelabs.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 C4A1A11E811A for <cdni@ietfa.amsl.com>; Fri, 24 May 2013 13:35:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.462
X-Spam-Level: 
X-Spam-Status: No, score=-100.462 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
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 d0hxjET0QphY for <cdni@ietfa.amsl.com>; Fri, 24 May 2013 13:35:09 -0700 (PDT)
Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by ietfa.amsl.com (Postfix) with ESMTP id EAF5311E811F for <cdni@ietf.org>; Fri, 24 May 2013 13:35:02 -0700 (PDT)
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.5/8.14.5) with ESMTP id r4OKYxPO026166; Fri, 24 May 2013 14:34:59 -0600
Received: from exchange.cablelabs.com (10.5.0.19) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/407/kyzyl.cablelabs.com); Fri, 24 May 2013 14:34:59 -0600 (MDT)
X-Virus-Status: clean(F-Secure/fsigk_smtp/407/kyzyl.cablelabs.com)
Received: from EXCHANGE.cablelabs.com ([fe80::797a:96d1:3c53:18ee]) by EXCHANGE.cablelabs.com ([fe80::797a:96d1:3c53:18ee%11]) with mapi id 14.03.0123.003; Fri, 24 May 2013 14:34:59 -0600
From: Daryl Malas <D.Malas@cablelabs.com>
To: "kleung@cisco.com" <kleung@cisco.com>, "yiu_lee@cable.comcast.com" <yiu_lee@cable.comcast.com>
Thread-Topic: [CDNi] Chair review of Requirements draft
Thread-Index: AQHOWL4ol8g/hXc8EEqlADDdC7rE1w==
Date: Fri, 24 May 2013 20:34:59 +0000
Message-ID: <CDC52B13.C1C6%d.malas@cablelabs.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.4.130416
x-originating-ip: [10.4.1.250]
Content-Type: multipart/alternative; boundary="_000_CDC52B13C1C6dmalascablelabscom_"
MIME-Version: 1.0
X-Approved: ondar
Cc: "cdni@ietf.org" <cdni@ietf.org>
Subject: [CDNi]  Chair review of Requirements draft
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, 24 May 2013 20:35:14 -0000

--_000_CDC52B13C1C6dmalascablelabscom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Kent and Yiu,

Here is my chair review of the requirements draft.  Overall, I think this d=
raft is in great shape.  Let me know if you have any questions.

Regards,

Daryl

Abstract:
I think the cdni WG charter actually describes the problem better than the =
text used in the draft.  I recommend better aligning with the charter text =
- "As a result of the significant growth in content delivered over IP netwo=
rks, existing CDN providers are scaling up their infrastructure and many Ne=
twork Service Providers and Enterprise Service Providers are deploying thei=
r own CDNs. Subject to the policy of the CSP, it is generally desirable tha=
t a given item of content can be delivered to an end user regardless of tha=
t end user's location or attachment network.  This creates a need for inter=
connecting (previously) standalone CDNs so they can interoperate and collec=
tively behave as a single delivery infrastructure."

Nit - "=85such CDN interconnection." to "=85such CDN interconnections."

Remove this sentence - "This draft is a work in progress and requirements m=
ay be added, modified, or removed by the working group."

The "Requirements Language" should be moved to the "Terminology" section.

Under the sub-bullets for "high, medium and low," I recommend we remove ref=
erences to compromising the working group's schedule.  Instead, change thes=
e comments to indicate the goal in assigning the varying priorities is rela=
tive to providing a "deployable solution in a short timeframe (18-24 months=
) as needed by the industry."  This is the goal as part of the working grou=
p charter.

Introduction:
My experience is that "subjective" language should be avoided in IETF draft=
s.  The introduction in this draft is full of subjective phrases: "rapidly =
increasing and expected to continue", "reduced delivery cost", "improved qu=
ality of experience", "increased robustness", "cost benefit and user experi=
ence".  At a minimum, I suggest removing some of this subjectivity and focu=
s on how CDNI will allow for content delivery across multiple CDNs.

In the last paragraph, instead of saying "In order to meet the timelines" -=
- see comment above regarding "short timeframe (18-24 months) as needed by =
the industry."

CDNI Control Interface Requirements:
The following sentence lends to discussing potential solutions.  "We observ=
e that while the CDNI Control interface is currently discussed as a single =
"protocol", further analysis will determine whether the corresponding requi=
rements are to be realized over a single interface and protocol, or over mu=
ltiple interfaces and protocols."  I suggest we remove this from this requi=
rement and make a statement at the beginning along the lines of, "The worki=
ng group attempted to align requirements with the appropriate interface; ho=
wever, solutions to these requirements may apply to a different interface o=
r another interface in addition to the interface it is associated with."

CI-1 =96 Suggest changing this requirement from "=85Downstream CDN (and, if=
 cascaded CDNs are supported by the solution, that the potential cascaded D=
ownstream CDNs) delete=85" to "=85Downstream CDN, including downstream casc=
aded CDNs, delete=85"  Apply this to CI-3, CI-4 and any other similar refer=
ences.  Since, we support cascaded CDNs, then we should simply specify the =
inclusion in the requirement.

CI-4 =96 I think we should require a "reason" to be included with a failure=
 response.  Initially it could simply be a string, unless we are going to s=
imply use HTTP response codes.

CI-8 - "CDNI interconnection" is redundant.  Also, I think "i.e." should be=
 "e.g.".

CDNI Request Routing/Redirection Interface Requirements:
RI-6 appears to be what RI-5 refers to with regards to the "loop prevention=
 mechanism".  If this is the case, I think we should add that language to R=
I-6 and change the order of these two.

CDNI Metadata Distribution Interface Requirements:
MI-16 has a list with only 1 bullet point.  I suggest changing it to, "For =
example, this could potentially including the need to validate URI signed i=
nformation (e.g.  Expiry time, Client IP address)."
MI-21 nit, "Streamin" to "Streaming"; and, this needs to be removed and add=
ressed "[Ed: need to improve wording?]"

CDNI Logging Interface Requirements:
[Same comment as in the CDNI Control Interface Requirements with regards to=
 noting whether it may or may not be multiple protocols.]
LI-13 nit, "requests on via the CDNI" to "requests via the CDNI"

CDNI Security Requirements:
Opening paragraph nit, "Some of those" to "Some of these".

>end.

--_000_CDC52B13C1C6dmalascablelabscom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <15A8326D666F75449EF8F5CC85EA1C51@cablelabs.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif; ">
<div>
<div>Kent and Yiu,</div>
<div><br>
</div>
<div>Here is my chair review of the requirements draft. &nbsp;Overall, I th=
ink this draft is in great shape. &nbsp;Let me know if you have any questio=
ns.</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Daryl</div>
<div><br>
</div>
<div>Abstract:</div>
<div>I think the cdni WG charter actually describes the problem better than=
 the text used in the draft. &nbsp;I recommend better aligning with the cha=
rter text - &quot;As a result of the significant growth in content delivere=
d over IP&nbsp;networks, existing CDN providers
 are scaling up their infrastructure and&nbsp;many Network Service Provider=
s and Enterprise Service Providers are&nbsp;deploying their own CDNs. Subje=
ct to the policy of the CSP, it is&nbsp;generally desirable that a given it=
em of content can be delivered to an&nbsp;end user regardless
 of that end user's location or attachment network. &nbsp;This creates a ne=
ed for interconnecting (previously) standalone CDNs so&nbsp;they can intero=
perate and collectively behave as a single delivery&nbsp;infrastructure.&qu=
ot;</div>
<div><br>
</div>
<div>Nit - &quot;=85such CDN interconnection.&quot; to &quot;=85such CDN in=
terconnections.&quot;</div>
<div><br>
</div>
<div>Remove this sentence - &quot;This draft is a work in progress and requ=
irements may be&nbsp;added, modified, or removed by the working group.&quot=
;</div>
<div><br>
</div>
<div>The &quot;Requirements Language&quot; should be moved to the &quot;Ter=
minology&quot; section.</div>
<div><br>
</div>
<div>Under the sub-bullets for &quot;high, medium and low,&quot; I recommen=
d we remove references to compromising the working group's schedule. &nbsp;=
Instead, change these comments to indicate the goal in assigning the varyin=
g priorities is relative to providing a &quot;deployable
 solution in a short timeframe (18-24 months) as&nbsp;needed by the industr=
y.&quot; &nbsp;This is the goal as part of the working group charter.</div>
<div><br>
</div>
<div>Introduction:</div>
<div>My experience is that &quot;subjective&quot; language should be avoide=
d in IETF drafts. &nbsp;The introduction in this draft is full of subjectiv=
e phrases: &quot;rapidly increasing and expected to continue&quot;, &quot;r=
educed delivery cost&quot;, &quot;improved quality of experience&quot;, &qu=
ot;increased&nbsp;robustness&quot;,
 &quot;cost&nbsp;benefit and user experience&quot;. &nbsp;At a minimum, I s=
uggest removing some of this subjectivity and focus on how CDNI will allow =
for content delivery across multiple CDNs.</div>
<div><br>
</div>
<div>In the last paragraph, instead of saying &quot;In order to meet the ti=
melines&quot; -- see comment above regarding &quot;short timeframe (18-24 m=
onths) as needed by the industry.&quot;</div>
<div><br>
</div>
<div>CDNI Control Interface Requirements:</div>
<div>The following sentence lends to discussing potential solutions. &nbsp;=
&quot;We observe that while the CDNI Control interface is&nbsp;currently di=
scussed as a single &quot;protocol&quot;, further analysis will&nbsp;determ=
ine whether the corresponding requirements are to be realized&nbsp;over
 a single interface and protocol, or over multiple interfaces and&nbsp;prot=
ocols.&quot; &nbsp;I suggest we remove this from this requirement and make =
a statement at the beginning along the lines of, &quot;The working group at=
tempted to align requirements with the appropriate interface;
 however, solutions to these requirements may apply to a different interfac=
e or another interface in addition to the interface it is associated with.&=
quot;</div>
<div><br>
</div>
<div>CI-1 =96 Suggest changing this requirement from &quot;=85Downstream CD=
N (and, if cascaded CDNs are&nbsp;supported by the solution, that the poten=
tial cascaded&nbsp;Downstream CDNs) delete=85&quot; to &quot;=85Downstream =
CDN, including downstream cascaded CDNs, delete=85&quot; &nbsp;Apply this t=
o
 CI-3, CI-4 and any other similar references. &nbsp;Since, we support casca=
ded CDNs, then we should simply specify the inclusion in the requirement.</=
div>
<div><br>
</div>
<div>CI-4 =96 I think we should require a &quot;reason&quot; to be included=
 with a failure response. &nbsp;Initially it could simply be a string, unle=
ss we are going to simply use HTTP response codes.</div>
<div><br>
</div>
<div>CI-8 - &quot;CDNI&nbsp;interconnection&quot; is redundant. &nbsp;Also,=
 I think &quot;i.e.&quot; should be &quot;e.g.&quot;.</div>
<div><br>
</div>
<div><font face=3D"Calibri,sans-serif">CDNI Request Routing/Redirection Int=
erface Requirements:</font></div>
<div>
<div>RI-6 appears to be what RI-5 refers to with regards to the &quot;loop =
prevention&nbsp;mechanism&quot;. &nbsp;If this is the case, I think we shou=
ld add that language to RI-6 and change the order of these two.</div>
<div><br>
</div>
<div><font face=3D"Calibri,sans-serif">CDNI Metadata Distribution Interface=
 Requirements:</font></div>
</div>
<div><font face=3D"Calibri,sans-serif">MI-16 has a list with only 1 bullet =
point. &nbsp;I&nbsp;suggest changing it to, &quot;</font><font face=3D"Cali=
bri,sans-serif">For example,&nbsp;</font>this could potentially including t=
he&nbsp;need to validate URI signed information (e.g. &nbsp;Expiry&nbsp;tim=
e,
 Client IP address).&quot;</div>
<div>MI-21 nit, &quot;<font face=3D"Calibri,sans-serif">Streamin&quot; to &=
quot;Streaming&quot;; and, this needs to be removed and addressed &quot;</f=
ont>[Ed: need&nbsp;to improve wording?]&quot;</div>
<div><br>
</div>
<div>CDNI Logging Interface Requirements:</div>
<div>[Same comment as in the CDNI Control Interface Requirements with regar=
ds to noting whether it may or may not be multiple protocols.]</div>
<div>LI-13 nit, &quot;requests on via the CDNI&quot; to &quot;requests via =
the CDNI&quot;</div>
<div><br>
</div>
<div>CDNI Security Requirements:</div>
<div>Opening paragraph nit, &quot;Some of those&quot; to &quot;Some of thes=
e&quot;.</div>
</div>
<br>
<div>&gt;end.</div>
</body>
</html>

--_000_CDC52B13C1C6dmalascablelabscom_--

From internet-drafts@ietf.org  Mon May 27 09:57:51 2013
Return-Path: <internet-drafts@ietf.org>
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 96BEA21F9700; Mon, 27 May 2013 09:57:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.362
X-Spam-Level: 
X-Spam-Status: No, score=-102.362 tagged_above=-999 required=5 tests=[AWL=0.238, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 qrKAP8XH3TnI; Mon, 27 May 2013 09:57:51 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 18A7921F8DB7; Mon, 27 May 2013 09:57:51 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.50
Message-ID: <20130527165750.6906.58669.idtracker@ietfa.amsl.com>
Date: Mon, 27 May 2013 09:57:51 -0700
Cc: cdni@ietf.org
Subject: [CDNi] I-D Action: draft-ietf-cdni-logging-02.txt
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: Mon, 27 May 2013 16:57:51 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Content Delivery Networks Interconnection=
 Working Group of the IETF.

	Title           : CDNI Logging Interface
	Author(s)       : Gilles Bertrand
                          Iuniana Oprescu
                          Francois Le Faucheur
                          Roy Peterkofsky
	Filename        : draft-ietf-cdni-logging-02.txt
	Pages           : 37
	Date            : 2013-05-27

Abstract:
   This memo specifies the Logging interface between a downstream CDN
   (dCDN) and an upstream CDN (uCDN) that are interconnected as per the
   CDN Interconnection (CDNI) framework.  First, it describes a
   reference model for CDNI logging.  Then, it specifies the CDNI
   Logging File format and the actual protocol for exchange of CDNI
   Logging Files.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-cdni-logging

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-cdni-logging-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cdni-logging-02


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From flefauch@cisco.com  Mon May 27 10:02:38 2013
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 AD9EB21F9717 for <cdni@ietfa.amsl.com>; Mon, 27 May 2013 10:02:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.584
X-Spam-Level: 
X-Spam-Status: No, score=-7.584 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, HTML_MESSAGE=0.001, J_CHICKENPOX_63=0.6, 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 3p2Q56cftCNt for <cdni@ietfa.amsl.com>; Mon, 27 May 2013 10:02:34 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id C883C21F9716 for <cdni@ietf.org>; Mon, 27 May 2013 10:02:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=27197; q=dns/txt; s=iport; t=1369674153; x=1370883753; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=AldHLxHCWMlYrO1z+FJ0Vi88JWjTIhzo43+Ibv2QAg4=; b=RIc6dZJ+WLHjib5VBYr1UefHkwlMjlAmNZgM4I+61SMkkvquzqFvSbeU XFDznrAZbd1SrqimfL+IZ4JyLbuvScaJSFpMG9/evRjT0OF8rbwTjNDjx Z2F3dNn9+hBh1v4TjdFlUmFu7VnYLYwnWRWD2ySEOZiVEXB1bYLG/MlF6 I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtMFAKuQo1GtJXG//2dsb2JhbABAFwOCREQwwgeBBhZtB4IkAQECAgEBAWMCBhsCAQgUDgoECAQDBycLFBABAgEDEwiIBQwzr26NJI1bG3YgAQsBCgERB4JbYQOoe4I/UIFxNg
X-IronPort-AV: E=Sophos;i="4.87,752,1363132800";  d="scan'208,217";a="215236158"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-1.cisco.com with ESMTP; 27 May 2013 17:02:33 +0000
Received: from xhc-aln-x04.cisco.com (xhc-aln-x04.cisco.com [173.36.12.78]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id r4RH2WB7015362 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <cdni@ietf.org>; Mon, 27 May 2013 17:02:32 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.56]) by xhc-aln-x04.cisco.com ([173.36.12.78]) with mapi id 14.02.0318.004; Mon, 27 May 2013 12:02:32 -0500
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "cdni@ietf.org" <cdni@ietf.org>
Thread-Topic: [CDNi] CDNI Logging - Series of Informal Meetings
Thread-Index: AQHOSinCyYxSJinUj0azs1JHewNx8Jj34h8QgABXo4CAIX2uAA==
Date: Mon, 27 May 2013 17:02:32 +0000
Message-ID: <FC236DA6F2DA77449EF2D02DF4471A8D62E927@xmb-rcd-x10.cisco.com>
References: <FC236DA6F2DA77449EF2D02DF4471A8D600780@xmb-rcd-x10.cisco.com> <32176_1367832523_518777CB_32176_694_1_5AE9CCAA1B4A2248AB61B4C7F0AD5FB906C34DC6@PEXCVZYM14.corporate.adroot.infra.ftgroup> <FC236DA6F2DA77449EF2D02DF4471A8D60161E@xmb-rcd-x10.cisco.com>
In-Reply-To: <FC236DA6F2DA77449EF2D02DF4471A8D60161E@xmb-rcd-x10.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.55.161.201]
Content-Type: multipart/alternative; boundary="_000_FC236DA6F2DA77449EF2D02DF4471A8D62E927xmbrcdx10ciscocom_"
MIME-Version: 1.0
Subject: Re: [CDNi] CDNI Logging - Series of Informal Meetings
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: Mon, 27 May 2013 17:02:38 -0000

--_000_FC236DA6F2DA77449EF2D02DF4471A8D62E927xmbrcdx10ciscocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Folks,

A new version of cdni-logging (-02) has just been posted. Please have a loo=
k at sections 3, 4 and 5 for discussion during Wed's informal meeting.

Note that this is only an interim working version and we expect to continue=
 rev up the document before Berlin, factoring in the upcoming discussions d=
uring the informal meetings.

Cheers

Francois


On 6 May 2013, at 11:36, Francois Le Faucheur (flefauch) <flefauch@cisco.co=
m<mailto:flefauch@cisco.com>> wrote:

Oops =85 correcting the typo pointed out by Emile in the last date:

These informal meetings will be run as Webex sessions on:
* Wed 29 May 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, fo=
r 90 minutes
* Wed 5 June 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, fo=
r 90 minutes
* Wed 26 June 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, f=
or 90 minutes

Francois

On 6 May 2013, at 11:28, emile.stephan@orange.com<mailto:emile.stephan@oran=
ge.com> wrote:

Hi Francois,

Just in case, is the third meeting planned for the 26 of June?

Regards
Emile

De : cdni-bounces@ietf.org<mailto:cdni-bounces@ietf.org> [mailto:cdni-bounc=
es@ietf.org<mailto:bounces@ietf.org>] De la part de Francois Le Faucheur (f=
lefauch)
Envoy=E9 : lundi 6 mai 2013 09:17
=C0 : cdni@ietf.org<mailto:cdni@ietf.org>
Objet : [CDNi] CDNI Logging - Series of Informal Meetings

Hi everyone,

(speaking as one of the cdni-logging co-authors)

We're in the process of revving up cdni-logging to reflect the Orlando disc=
ussions/conclusions. To maximise progress before Berlin, we'll run a series=
 of informal meetings to :
* collect feedback on interim versions of the I-D
* get input on the open items.

These informal meetings will be run as Webex sessions on:
* Wed 29 May 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, fo=
r 90 minutes
* Wed 5 June 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, fo=
r 90 minutes
* Wed 26 May 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, fo=
r 90 minutes

Please try attend and mark these slots in your calendar.

Cheers

Francois & cdni-logging co-authors

PS: Webex details below



=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Topic: IETF CDNI Logging - Informal Meeting
Date: Wednesday, May 29, 2013
Time: 5:00 pm, Europe Summer Time (Paris, GMT+02:00)
Meeting Number: 205 636 967
Password: cdni

-------------------------------------------------------
To join the meeting online(Now from mobile devices!)
-------------------------------------------------------
1. Go to https://cisco.webex.com/ciscosales/j.php?ED=3D225213752&UID=3D4843=
18167&PW=3DNNTMwZTVjNGRk&RT=3DMiMyMw%3D%3D
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: cdni
4. Click "Join".
5. If the meeting includes a teleconference, follow the instructions that a=
ppear on your screen.

-------------------------------------------------------
To join the audio conference only
-------------------------------------------------------
To receive a call back, provide your phone number when you join the meeting=
, or call the number below and enter the access code.
Call-in toll-free number (US/Canada): +1-866-432-9903
Call-in toll number (US/Canada): +1-408-525-6800
Toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restricti=
ons.pdf

Access code:205 636 967

CCP:+14085256800x205636967#

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D


Topic: IETF CDNI Logging - Informal Meeting
Date: Wednesday, June 5, 2013
Time: 5:00 pm, Europe Summer Time (Paris, GMT+02:00)
Meeting Number: 206 470 738
Password: cdni

-------------------------------------------------------
To join the meeting online(Now from mobile devices!)
-------------------------------------------------------
1. Go to https://cisco.webex.com/ciscosales/j.php?ED=3D225213782&UID=3D4843=
18167&PW=3DNMmQzODVmZjJm&RT=3DMiMyMw%3D%3D
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: cdni
4. Click "Join".
5. If the meeting includes a teleconference, follow the instructions that a=
ppear on your screen.

-------------------------------------------------------
To join the audio conference only
-------------------------------------------------------
To receive a call back, provide your phone number when you join the meeting=
, or call the number below and enter the access code.
Call-in toll-free number (US/Canada): +1-866-432-9903
Call-in toll number (US/Canada): +1-408-525-6800
Toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restricti=
ons.pdf

Access code:206 470 738

CCP:+14085256800x206470738#

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Topic: IETF CDNI Logging - Informal Meeting
Date: Wednesday, June 26, 2013
Time: 5:00 pm, Europe Summer Time (Paris, GMT+02:00)
Meeting Number: 208 330 914
Password: cdni

-------------------------------------------------------
To join the meeting online(Now from mobile devices!)
-------------------------------------------------------
1. Go to https://cisco.webex.com/ciscosales/j.php?ED=3D225213802&UID=3D4843=
18167&PW=3DNNzQ0ZmZmNjUz&RT=3DMiMyMw%3D%3D
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: cdni
4. Click "Join".
5. If the meeting includes a teleconference, follow the instructions that a=
ppear on your screen.

-------------------------------------------------------
To join the audio conference only
-------------------------------------------------------
To receive a call back, provide your phone number when you join the meeting=
, or call the number below and enter the access code.
Call-in toll-free number (US/Canada): +1-866-432-9903
Call-in toll number (US/Canada): +1-408-525-6800
Toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restricti=
ons.pdf

Access code:208 330 914

CCP:+14085256800x208330914#

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
IMPORTANT NOTICE: This WebEx service includes a feature that allows audio a=
nd any documents and other materials exchanged or viewed during the session=
 to be recorded. By joining this session, you automatically consent to such=
 recordings. If you do not consent to the recording, discuss your concerns =
with the meeting host prior to the start of the recording or do not join th=
e session. Please note that any such recordings may be subject to discovery=
 in the event of litigation.

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for message=
s that have been modified, changed or falsified.
Thank you.


_______________________________________________
CDNi mailing list
CDNi@ietf.org<mailto:CDNi@ietf.org>
https://www.ietf.org/mailman/listinfo/cdni


--_000_FC236DA6F2DA77449EF2D02DF4471A8D62E927xmbrcdx10ciscocom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <E813461B9EDDA246B80D9B20DE621CC4@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
Folks,
<div><br>
</div>
<div>A new version of cdni-logging (-02) has just been posted. Please have =
a look at sections 3, 4 and 5 for discussion during Wed's informal meeting.=
</div>
<div><br>
</div>
<div>Note that this is only an interim working version and we expect to con=
tinue rev up the document before Berlin, factoring in the upcoming discussi=
ons during the informal meetings.</div>
<div><br>
</div>
<div>Cheers</div>
<div><br>
</div>
<div>Francois</div>
<div><br>
</div>
<div><br>
<div>
<div>On 6 May 2013, at 11:36, Francois Le Faucheur (flefauch) &lt;<a href=
=3D"mailto:flefauch@cisco.com">flefauch@cisco.com</a>&gt; wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite"><base href=3D"x-msg://829/">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; ">
<div>Oops =85 correcting the typo pointed out by Emile in the last date:</d=
iv>
<div><br>
</div>
<div>These informal meetings will be run as Webex sessions on:<br>
* Wed 29 May 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, fo=
r 90 minutes<br>
* Wed 5 June 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, fo=
r 90 minutes<br>
* Wed 26 June 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, f=
or 90 minutes</div>
<div><br>
</div>
<div>Francois</div>
<br>
<div>
<div>On 6 May 2013, at 11:28, <a href=3D"mailto:emile.stephan@orange.com">e=
mile.stephan@orange.com</a> wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div lang=3D"FR" link=3D"blue" vlink=3D"purple" style=3D"font-family: Helve=
tica; font-size: medium; font-style: normal; font-variant: normal; font-wei=
ght: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-=
align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: n=
ormal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webki=
t-text-stroke-width: 0px; ">
<div class=3D"WordSection1" style=3D"page: WordSection1; ">
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<span lang=3D"EN-US">Hi Francois,<o:p></o:p></span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<span lang=3D"EN-US">&nbsp;</span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<span lang=3D"EN-US">Just in case, is the third meeting planned for the 26 =
of June?<o:p></o:p></span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<span lang=3D"EN-US" style=3D"font-size: 11pt; font-family: Calibri, sans-s=
erif; color: rgb(31, 73, 125); ">&nbsp;</span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<span lang=3D"EN-US">Regards<o:p></o:p></span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<span lang=3D"EN-US">Emile<o:p></o:p></span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<span lang=3D"EN-US" style=3D"font-size: 11pt; font-family: Calibri, sans-s=
erif; color: rgb(31, 73, 125); ">&nbsp;</span></div>
<div>
<div style=3D"border-style: solid none none; border-top-width: 1pt; border-=
top-color: rgb(181, 196, 223); padding: 3pt 0cm 0cm; ">
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<b><span style=3D"font-size: 10pt; font-family: Tahoma, sans-serif; ">De&nb=
sp;:</span></b><span style=3D"font-size: 10pt; font-family: Tahoma, sans-se=
rif; "><span class=3D"Apple-converted-space">&nbsp;</span><a href=3D"mailto=
:cdni-bounces@ietf.org" style=3D"color: purple; text-decoration: underline;=
 ">cdni-bounces@ietf.org</a><span class=3D"Apple-converted-space">&nbsp;</s=
pan>[mailto:cdni-<a href=3D"mailto:bounces@ietf.org" style=3D"color: purple=
; text-decoration: underline; ">bounces@ietf.org</a>]<span class=3D"Apple-c=
onverted-space">&nbsp;</span><b>De
 la part de</b><span class=3D"Apple-converted-space">&nbsp;</span>Francois =
Le Faucheur (flefauch)<br>
<b>Envoy=E9&nbsp;:</b><span class=3D"Apple-converted-space">&nbsp;</span>lu=
ndi 6 mai 2013 09:17<br>
<b>=C0&nbsp;:</b><span class=3D"Apple-converted-space">&nbsp;</span><a href=
=3D"mailto:cdni@ietf.org" style=3D"color: purple; text-decoration: underlin=
e; ">cdni@ietf.org</a><br>
<b>Objet&nbsp;:</b><span class=3D"Apple-converted-space">&nbsp;</span>[CDNi=
] CDNI Logging - Series of Informal Meetings<o:p></o:p></span></div>
</div>
</div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<o:p>&nbsp;</o:p></div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
Hi everyone,<o:p></o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<o:p>&nbsp;</o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
(speaking as one of the cdni-logging co-authors)<o:p></o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<o:p>&nbsp;</o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
We're in the process of revving up cdni-logging to reflect the Orlando disc=
ussions/conclusions. To maximise progress before Berlin, we'll run&nbsp;a s=
eries of informal meetings to :<o:p></o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
*&nbsp;collect feedback on&nbsp;interim versions of the I-D&nbsp;<o:p></o:p=
></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
* get&nbsp;input on the open items.<o:p></o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<o:p>&nbsp;</o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
These informal meetings will be run as Webex sessions on:<o:p></o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
* Wed 29 May 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, fo=
r 90 minutes<o:p></o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
* Wed 5 June 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, fo=
r 90 minutes<o:p></o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
* Wed 26 May 2013, at 08:0 Pacific Time =3D 17:00 Central European Time, fo=
r 90 minutes<span class=3D"apple-tab-span"><o:p></o:p></span></div>
</div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<o:p></o:p></div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<o:p>&nbsp;</o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
Please try attend and mark these slots in your calendar.<o:p></o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<o:p>&nbsp;</o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
Cheers<o:p></o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<o:p>&nbsp;</o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
Francois &amp; cdni-logging co-authors<o:p></o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<o:p>&nbsp;</o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
PS: Webex details below<o:p></o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<o:p>&nbsp;</o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<o:p>&nbsp;</o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<o:p>&nbsp;</o:p></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
<span style=3D"font-family: Tahoma, sans-serif; "><br>
Topic: IETF CDNI Logging - Informal Meeting&nbsp;<br>
<b><span style=3D"color: rgb(145, 38, 4); ">Date: Wednesday, May 29, 2013&n=
bsp;</span></b><br>
Time: 5:00 pm, Europe Summer Time (Paris, GMT&#43;02:00)&nbsp;<br>
Meeting Number: 205 636 967&nbsp;<br>
Password: cdni&nbsp;<br>
<br>
-------------------------------------------------------&nbsp;<br>
To join the meeting online(Now from mobile devices!)&nbsp;<br>
-------------------------------------------------------&nbsp;<br>
1. Go to&nbsp;</span><a href=3D"https://cisco.webex.com/ciscosales/j.php?ED=
=3D225213752&amp;UID=3D484318167&amp;PW=3DNNTMwZTVjNGRk&amp;RT=3DMiMyMw%3D%=
3D" target=3D"_blank" style=3D"color: purple; text-decoration: underline; "=
><span style=3D"font-family: Tahoma, sans-serif; ">https://cisco.webex.com/=
ciscosales/j.php?ED=3D225213752&amp;UID=3D484318167&amp;PW=3DNNTMwZTVjNGRk&=
amp;RT=3DMiMyMw%3D%3D</span></a><span style=3D"font-family: Tahoma, sans-se=
rif; ">&nbsp;<br>
2. If requested, enter your name and email address.&nbsp;<br>
3. If a password is required, enter the meeting password: cdni&nbsp;<br>
4. Click &quot;Join&quot;.&nbsp;<br>
5. If the meeting includes a teleconference, follow the instructions that a=
ppear on your screen.&nbsp;<br>
<br>
-------------------------------------------------------&nbsp;<br>
To join the audio conference only&nbsp;<br>
-------------------------------------------------------&nbsp;<br>
To receive a call back, provide your phone number when you join the meeting=
, or call the number below and enter the access code.&nbsp;<br>
Call-in toll-free number (US/Canada): &#43;1-866-432-9903&nbsp;<br>
Call-in toll number (US/Canada): &#43;1-408-525-6800&nbsp;<br>
Toll-free dialing restrictions:&nbsp;</span><a href=3D"http://www.webex.com=
/pdf/tollfree_restrictions.pdf" target=3D"_blank" style=3D"color: purple; t=
ext-decoration: underline; "><span style=3D"font-family: Tahoma, sans-serif=
; ">http://www.webex.com/pdf/tollfree_restrictions.pdf</span></a><span styl=
e=3D"font-family: Tahoma, sans-serif; ">&nbsp;<br>
<br>
Access code:205 636 967&nbsp;<br>
<br>
CCP:&#43;14085256800x205636967#&nbsp;<br>
</span><br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D<br>
<br>
<br>
<span style=3D"font-family: Tahoma, sans-serif; ">Topic: IETF CDNI Logging =
- Informal Meeting&nbsp;<br>
<b><span style=3D"color: rgb(145, 38, 4); ">Date: Wednesday, June 5, 2013&n=
bsp;</span></b><br>
Time: 5:00 pm, Europe Summer Time (Paris, GMT&#43;02:00)&nbsp;<br>
Meeting Number: 206 470 738&nbsp;<br>
Password: cdni&nbsp;<br>
<br>
-------------------------------------------------------&nbsp;<br>
To join the meeting online(Now from mobile devices!)&nbsp;<br>
-------------------------------------------------------&nbsp;<br>
1. Go to&nbsp;</span><a href=3D"https://cisco.webex.com/ciscosales/j.php?ED=
=3D225213782&amp;UID=3D484318167&amp;PW=3DNMmQzODVmZjJm&amp;RT=3DMiMyMw%3D%=
3D" target=3D"_blank" style=3D"color: purple; text-decoration: underline; "=
><span style=3D"font-family: Tahoma, sans-serif; ">https://cisco.webex.com/=
ciscosales/j.php?ED=3D225213782&amp;UID=3D484318167&amp;PW=3DNMmQzODVmZjJm&=
amp;RT=3DMiMyMw%3D%3D</span></a><span style=3D"font-family: Tahoma, sans-se=
rif; ">&nbsp;<br>
2. If requested, enter your name and email address.&nbsp;<br>
3. If a password is required, enter the meeting password: cdni&nbsp;<br>
4. Click &quot;Join&quot;.&nbsp;<br>
5. If the meeting includes a teleconference, follow the instructions that a=
ppear on your screen.&nbsp;<br>
<br>
-------------------------------------------------------&nbsp;<br>
To join the audio conference only&nbsp;<br>
-------------------------------------------------------&nbsp;<br>
To receive a call back, provide your phone number when you join the meeting=
, or call the number below and enter the access code.&nbsp;<br>
Call-in toll-free number (US/Canada): &#43;1-866-432-9903&nbsp;<br>
Call-in toll number (US/Canada): &#43;1-408-525-6800&nbsp;<br>
Toll-free dialing restrictions:&nbsp;</span><a href=3D"http://www.webex.com=
/pdf/tollfree_restrictions.pdf" target=3D"_blank" style=3D"color: purple; t=
ext-decoration: underline; "><span style=3D"font-family: Tahoma, sans-serif=
; ">http://www.webex.com/pdf/tollfree_restrictions.pdf</span></a><span styl=
e=3D"font-family: Tahoma, sans-serif; ">&nbsp;<br>
<br>
Access code:206 470 738&nbsp;<br>
<br>
CCP:&#43;14085256800x206470738#&nbsp;</span><br>
<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
<br>
<span style=3D"font-family: Tahoma, sans-serif; ">Topic: IETF CDNI Logging =
- Informal Meeting&nbsp;<br>
<b><span style=3D"color: rgb(145, 38, 4); ">Date: Wednesday, June 26, 2013&=
nbsp;</span></b><br>
Time: 5:00 pm, Europe Summer Time (Paris, GMT&#43;02:00)&nbsp;<br>
Meeting Number: 208 330 914&nbsp;<br>
Password: cdni&nbsp;<br>
<br>
-------------------------------------------------------&nbsp;<br>
To join the meeting online(Now from mobile devices!)&nbsp;<br>
-------------------------------------------------------&nbsp;<br>
1. Go to&nbsp;</span><a href=3D"https://cisco.webex.com/ciscosales/j.php?ED=
=3D225213802&amp;UID=3D484318167&amp;PW=3DNNzQ0ZmZmNjUz&amp;RT=3DMiMyMw%3D%=
3D" target=3D"_blank" style=3D"color: purple; text-decoration: underline; "=
><span style=3D"font-family: Tahoma, sans-serif; ">https://cisco.webex.com/=
ciscosales/j.php?ED=3D225213802&amp;UID=3D484318167&amp;PW=3DNNzQ0ZmZmNjUz&=
amp;RT=3DMiMyMw%3D%3D</span></a><span style=3D"font-family: Tahoma, sans-se=
rif; ">&nbsp;<br>
2. If requested, enter your name and email address.&nbsp;<br>
3. If a password is required, enter the meeting password: cdni&nbsp;<br>
4. Click &quot;Join&quot;.&nbsp;<br>
5. If the meeting includes a teleconference, follow the instructions that a=
ppear on your screen.&nbsp;<br>
<br>
-------------------------------------------------------&nbsp;<br>
To join the audio conference only&nbsp;<br>
-------------------------------------------------------&nbsp;<br>
To receive a call back, provide your phone number when you join the meeting=
, or call the number below and enter the access code.&nbsp;<br>
Call-in toll-free number (US/Canada): &#43;1-866-432-9903&nbsp;<br>
Call-in toll number (US/Canada): &#43;1-408-525-6800&nbsp;<br>
Toll-free dialing restrictions:&nbsp;</span><a href=3D"http://www.webex.com=
/pdf/tollfree_restrictions.pdf" target=3D"_blank" style=3D"color: purple; t=
ext-decoration: underline; "><span style=3D"font-family: Tahoma, sans-serif=
; ">http://www.webex.com/pdf/tollfree_restrictions.pdf</span></a><span styl=
e=3D"font-family: Tahoma, sans-serif; ">&nbsp;<br>
<br>
Access code:208 330 914&nbsp;<br>
<br>
CCP:&#43;14085256800x208330914#&nbsp;<br>
</span><br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<span style=3D"font-family: Tahoma, =
sans-serif; "><br>
IMPORTANT NOTICE: This WebEx service includes a feature that allows audio a=
nd any documents and other materials exchanged or viewed during the session=
 to be recorded. By joining this session, you automatically consent to such=
 recordings. If you do not consent
 to the recording, discuss your concerns with the meeting host prior to the=
 start of the recording or do not join the session. Please note that any su=
ch recordings may be subject to discovery in the event of litigation.&nbsp;=
</span><o:p></o:p></div>
</div>
</div>
<pre>______________________________________________________________________=
___________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for message=
s that have been modified, changed or falsified.
Thank you.
</pre>
</div>
</blockquote>
</div>
<br>
</div>
_______________________________________________<br>
CDNi mailing list<br>
<a href=3D"mailto:CDNi@ietf.org">CDNi@ietf.org</a><br>
https://www.ietf.org/mailman/listinfo/cdni<br>
</blockquote>
</div>
<br>
</div>
</body>
</html>

--_000_FC236DA6F2DA77449EF2D02DF4471A8D62E927xmbrcdx10ciscocom_--

From ben@niven-jenkins.co.uk  Tue May 28 00:53:15 2013
Return-Path: <ben@niven-jenkins.co.uk>
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 F295921F91BC for <cdni@ietfa.amsl.com>; Tue, 28 May 2013 00:53:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.599
X-Spam-Level: 
X-Spam-Status: No, score=-104.599 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 RyI+6sVvX-9D for <cdni@ietfa.amsl.com>; Tue, 28 May 2013 00:53:08 -0700 (PDT)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.61]) by ietfa.amsl.com (Postfix) with ESMTP id BB9DE21F9123 for <cdni@ietf.org>; Tue, 28 May 2013 00:53:07 -0700 (PDT)
Received: from cpc4-cmbg17-2-0-cust814.5-4.cable.virginmedia.com ([86.14.227.47] helo=[192.168.0.4]) by mail4.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1UhEiP-0002Qk-KV for cdni@ietf.org; Tue, 28 May 2013 08:53:05 +0100
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Tue, 28 May 2013 08:53:05 +0100
Message-Id: <4ED9B258-F1EC-4F49-AE0E-864E5826AB2A@niven-jenkins.co.uk>
To: cdni@ietf.org
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Subject: [CDNi] CDNI Logging - Origin directive
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: Tue, 28 May 2013 07:53:15 -0000

Colleagues,

draft-ietf-cdni-logging-02 states:

   o  Origin:

      *  format: <host>

      *  semantic: this identifies the entity transmitting the CDNI
         Logging File (e.g.  the host in a dCDN supporting the CDNI
         Logging interface) or the entity responsible for transmitting
         the CDNI Logging File (e.g.  the dCDN).

      *  occurrence: there MUST be zero or one instance of this
         directive.  This directive MAY be included by the
         implementation transmitting the CDNI Logging file.  When
         included by the transmitting side, it MUST be validated or
         over-written by the receiving side.  When, it is not included
         by the transmitting side, it MAY be added locally by the
         receiving side.  [Editor's Note if we include a non-repudiation
         mechanism: discuss the fact that this will provide incentive to
         dCDN to not cheat , as it can be detected]

Why MUST the Origin directive be validated or over-written by the =
receiving side and how is the receiving side meant to perform validation =
on the contents of this directive?

Thanks
Ben


From ben@niven-jenkins.co.uk  Tue May 28 01:01:40 2013
Return-Path: <ben@niven-jenkins.co.uk>
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 C4BAD21F8EC2 for <cdni@ietfa.amsl.com>; Tue, 28 May 2013 01:01:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.932
X-Spam-Level: 
X-Spam-Status: No, score=-103.932 tagged_above=-999 required=5 tests=[AWL=-1.333, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 9bEPjKyjHclk for <cdni@ietfa.amsl.com>; Tue, 28 May 2013 01:01:32 -0700 (PDT)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.62]) by ietfa.amsl.com (Postfix) with ESMTP id 7F57321F8D90 for <cdni@ietf.org>; Tue, 28 May 2013 01:01:32 -0700 (PDT)
Received: from cpc4-cmbg17-2-0-cust814.5-4.cable.virginmedia.com ([86.14.227.47] helo=[192.168.0.4]) by mail12.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1UhEqZ-0006tL-Jw for cdni@ietf.org; Tue, 28 May 2013 09:01:31 +0100
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Tue, 28 May 2013 09:01:31 +0100
Message-Id: <617086B6-30C5-457F-AF75-046E7F496035@niven-jenkins.co.uk>
To: cdni@ietf.org
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Subject: [CDNi] CDNI Logging - whitespace
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: Tue, 28 May 2013 08:01:40 -0000

Colleagues,

Reading draft-ietf-cdni-logging-02 Section 3.1:

   o  Fields:

      *  format: <field-name>[ <field-name>], where the allowed list of
         <field-name> are specified for each Record-Type in Section 3.2

      *  semantic: this lists the names of all the fields for which a
         value is to appear in the CDNI Logging Records that are after
         this directive.  The names of the fields, as well as their
         possible occurrences, are specified for each type of CDNI
         Logging Records in Section 3.2. The field names listed in this
         directive MUST be separated by a whitespace (" ").

Does this mean separated by any whitespace or specifically by a single =
(or multiple?) space character?

(Section 3.2 specifies TAB MUST be used to separate the actual field =
values in the log)

Thanks
Ben


From ben@niven-jenkins.co.uk  Tue May 28 01:08:00 2013
Return-Path: <ben@niven-jenkins.co.uk>
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 9793421F9216 for <cdni@ietfa.amsl.com>; Tue, 28 May 2013 01:07:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 M+yQSnrgEMr1 for <cdni@ietfa.amsl.com>; Tue, 28 May 2013 01:07:52 -0700 (PDT)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.61]) by ietfa.amsl.com (Postfix) with ESMTP id E0F6A21F92CB for <cdni@ietf.org>; Tue, 28 May 2013 01:07:49 -0700 (PDT)
Received: from cpc4-cmbg17-2-0-cust814.5-4.cable.virginmedia.com ([86.14.227.47] helo=[192.168.0.4]) by mail11.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1UhEwd-0005mC-PR for cdni@ietf.org; Tue, 28 May 2013 09:07:47 +0100
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Tue, 28 May 2013 09:07:47 +0100
Message-Id: <69F22737-24DE-4835-A2B5-1EAEDAA6A705@niven-jenkins.co.uk>
To: cdni@ietf.org
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Subject: [CDNi] CDNI Logging date & time
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: Tue, 28 May 2013 08:08:01 -0000

Colleagues,

draft-cdni-logging-02 section 3.2.1 specifies:

   o  date:

      *  format: <date>

      *  semantic: the date at which the processing of request started
         on the Surrogate.

      *  occurrence: there MUST be one and only one instance of this
         field.

   o  time:

      *  format: <time>

      *  semantic: the time at which the processing of request started
         on the Surrogate.

      *  occurrence: there MUST be one and only one instance of this
         field.

Can we make these the end date/time instead of the start date/time?

It makes the logs themselves a little easier to parse/read as the dates =
will be chronological rather than jumping over the place depending on =
start time/response size/etc. End date/time can still be calculated from =
start date/time+time-taken if it is required.

Thanks
Ben


From ben@niven-jenkins.co.uk  Tue May 28 01:16:25 2013
Return-Path: <ben@niven-jenkins.co.uk>
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 29F8521F8E6E for <cdni@ietfa.amsl.com>; Tue, 28 May 2013 01:16:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.399
X-Spam-Level: 
X-Spam-Status: No, score=-103.399 tagged_above=-999 required=5 tests=[AWL=-0.800, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 v+w7gIZ+czyj for <cdni@ietfa.amsl.com>; Tue, 28 May 2013 01:16:15 -0700 (PDT)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.61]) by ietfa.amsl.com (Postfix) with ESMTP id BA45221F859D for <cdni@ietf.org>; Tue, 28 May 2013 01:16:13 -0700 (PDT)
Received: from cpc4-cmbg17-2-0-cust814.5-4.cable.virginmedia.com ([86.14.227.47] helo=[192.168.0.4]) by mail11.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1UhF4m-00074o-CI for cdni@ietf.org; Tue, 28 May 2013 09:16:12 +0100
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Tue, 28 May 2013 09:16:11 +0100
Message-Id: <39F159F6-E86A-4464-AF44-C5EE7A48F8CE@niven-jenkins.co.uk>
To: cdni@ietf.org
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Subject: [CDNi] CDNI Logging - cs-uri
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: Tue, 28 May 2013 08:16:25 -0000

Colleagues,

draft-cdni-logging-02 section 3.2.1 states:

   o  cs-uri: [Editor's note: rename "sr-uri" ?]

      *  format: <uri>

      *  semantic: this is the absolute-URI of the request received by
         the Surrogate.  [Editor's Note: do we agree this should be an
         absolute-URI even if teh request uses a relative-URI?]

      *  occurrence: there MUST be zero or exactly one instance of this
         field.

It is cs-uri because it is the URI the User Agent presented to the =
surrogate. sr-uri would be the URI that the surrogate presented to its =
upstream source on a cache miss.

It should be the absolute URI as specified in the Request-URI (if the =
Request-URI includes a host) or an absolute URI constructed from the =
Host + Request-URI IMO.

Ben


From flefauch@cisco.com  Tue May 28 01:37:37 2013
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 B192821F919D for <cdni@ietfa.amsl.com>; Tue, 28 May 2013 01:37:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.091
X-Spam-Level: 
X-Spam-Status: No, score=-9.091 tagged_above=-999 required=5 tests=[AWL=1.508,  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 r0I-evUPP8Us for <cdni@ietfa.amsl.com>; Tue, 28 May 2013 01:37:31 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 7D12F21F87D1 for <cdni@ietf.org>; Tue, 28 May 2013 01:37:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2494; q=dns/txt; s=iport; t=1369730249; x=1370939849; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=rcOHG72aSMvC9xZUKkBDPsheMCSDH0ZNz2wGvEntq8M=; b=mp+P1gMJpy50ZqsqiCnuLa9QZnKpTPpPwuoY11EfjHKH7gZDd6Yjrqjy RCO/Oizf5kFveegE9bY2fylsI1pOln4g1L+k2cnDyzzntXW1YdnI4FSpb G+w0FzXyt0pJ4mNHk/5HzCDLQb31Dv1nmrPc/Ddenvjdy1aze7JyfryIa Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmwFABxspFGtJXHB/2dsb2JhbABQCYMIMMISgQUWdIIjAQEBAwEBAQE3NAQHBQsCAQgiFBAnCyUCBA4FCId/Bgy7eASNYoEIAjEHgnNhA6h7gw+BaiQZ
X-IronPort-AV: E=Sophos;i="4.87,756,1363132800"; d="scan'208";a="215610657"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-8.cisco.com with ESMTP; 28 May 2013 08:37:29 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r4S8bSVX020356 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 28 May 2013 08:37:28 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.56]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.02.0318.004; Tue, 28 May 2013 03:37:28 -0500
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Thread-Topic: [CDNi] CDNI Logging - Origin directive
Thread-Index: AQHOW3htOA6G3dAV/EaKG3k6lq75CZkamgwA
Date: Tue, 28 May 2013 08:37:28 +0000
Message-ID: <FC236DA6F2DA77449EF2D02DF4471A8D62FB2F@xmb-rcd-x10.cisco.com>
References: <4ED9B258-F1EC-4F49-AE0E-864E5826AB2A@niven-jenkins.co.uk>
In-Reply-To: <4ED9B258-F1EC-4F49-AE0E-864E5826AB2A@niven-jenkins.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.55.161.201]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <DF98F48FD7A4BC4D99F2B296335B9436@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<cdni@ietf.org>" <cdni@ietf.org>
Subject: Re: [CDNi] CDNI Logging - Origin directive
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: Tue, 28 May 2013 08:37:37 -0000

Hi Ben, (and all)

Thanks for reviewing the doc. Also using a separate thread per issue will h=
elp us.=20
To your first comment:

On 28 May 2013, at 09:53, Ben Niven-Jenkins <ben@niven-jenkins.co.uk> wrote=
:

> Colleagues,
>=20
> draft-ietf-cdni-logging-02 states:
>=20
>   o  Origin:
>=20
>      *  format: <host>
>=20
>      *  semantic: this identifies the entity transmitting the CDNI
>         Logging File (e.g.  the host in a dCDN supporting the CDNI
>         Logging interface) or the entity responsible for transmitting
>         the CDNI Logging File (e.g.  the dCDN).
>=20
>      *  occurrence: there MUST be zero or one instance of this
>         directive.  This directive MAY be included by the
>         implementation transmitting the CDNI Logging file.  When
>         included by the transmitting side, it MUST be validated or
>         over-written by the receiving side.  When, it is not included
>         by the transmitting side, it MAY be added locally by the
>         receiving side.  [Editor's Note if we include a non-repudiation
>         mechanism: discuss the fact that this will provide incentive to
>         dCDN to not cheat , as it can be detected]
>=20
> Why MUST the Origin directive be validated or over-written by the receivi=
ng side and how is the receiving side meant to perform validation on the co=
ntents of this directive?


Perhaps a "MAY" would be more appropriate. Right?

In any case, here is how I picture the "Origin" field:
	* that field is intended to be a reliable record of the log file origin
	* the uCDN is ultimately responsible (to itself) for the accuracy of that =
field. To do that it can select the approach it sees best fit among several=
 candidate approaches including:
		- uCDN establishes identity of the entity that transmitted the Log file v=
ia security mechanisms that are part of the CDNI log file exchange protocol=
 (HTTPS) and then uCDN writes/overwrites this field
		- uCDN relies on dCDN to populate that field and then relies on non-repud=
iation mechanism to act as incentive for dCDN to not lie (or relies on spec=
ial trust relationship with dCDN -eg it is part of the same administrative =
entity- to not lie)  .
Does that make sense? If yes, maybe we can tweak text to explain this bette=
r.

> Thanks
> Ben
>=20
> _______________________________________________
> CDNi mailing list
> CDNi@ietf.org
> https://www.ietf.org/mailman/listinfo/cdni


From flefauch@cisco.com  Tue May 28 01:40:01 2013
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 6D44721F92EC for <cdni@ietfa.amsl.com>; Tue, 28 May 2013 01:40:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.845
X-Spam-Level: 
X-Spam-Status: No, score=-9.845 tagged_above=-999 required=5 tests=[AWL=0.754,  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 5Eah+XVDJhbO for <cdni@ietfa.amsl.com>; Tue, 28 May 2013 01:39:54 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 6616321F8700 for <cdni@ietf.org>; Tue, 28 May 2013 01:39:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1298; q=dns/txt; s=iport; t=1369730393; x=1370939993; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=IHZQ7s5NnqJL2JNpIIWDis7dr0Q2+wgRXRLtOapP//Y=; b=E9nv7En8JDI4EXv1lMW8UsmWlj6I7JaSUJBvfB1Tfim+zg5fqFPordMY MjUW8pehikYQs5jm4GLph41UgO1xl6/C9TbGwb7jNPN0KqMHcZF/+2EHF 8P9pQbKepWo1/dj0irFXUHdRyfZlyht2XBEPc+xjxu72vy9SOPvkATtrN I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmwFAIlspFGtJV2Y/2dsb2JhbABZgwgwwhKBBRZ0giMBAQEDAQEBATc0CwULAgEIIhQQJwslAgQOBQiHfwYMu3oEjmoCMQeCc2EDqHuDD4In
X-IronPort-AV: E=Sophos;i="4.87,756,1363132800"; d="scan'208";a="215641278"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-3.cisco.com with ESMTP; 28 May 2013 08:39:53 +0000
Received: from xhc-aln-x07.cisco.com (xhc-aln-x07.cisco.com [173.36.12.81]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r4S8dqEI002736 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 28 May 2013 08:39:52 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.56]) by xhc-aln-x07.cisco.com ([173.36.12.81]) with mapi id 14.02.0318.004; Tue, 28 May 2013 03:39:52 -0500
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Thread-Topic: [CDNi] CDNI Logging - whitespace
Thread-Index: AQHOW3nFR8FSDAmDH0ib1NZiSkcA6JkamrSA
Date: Tue, 28 May 2013 08:39:51 +0000
Message-ID: <FC236DA6F2DA77449EF2D02DF4471A8D62FB5A@xmb-rcd-x10.cisco.com>
References: <617086B6-30C5-457F-AF75-046E7F496035@niven-jenkins.co.uk>
In-Reply-To: <617086B6-30C5-457F-AF75-046E7F496035@niven-jenkins.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.55.161.201]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <64A9DC6FCA0F724EA31ADABDD73C1556@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<cdni@ietf.org>" <cdni@ietf.org>
Subject: Re: [CDNi] CDNI Logging - whitespace
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: Tue, 28 May 2013 08:40:01 -0000

On 28 May 2013, at 10:01, Ben Niven-Jenkins <ben@niven-jenkins.co.uk> wrote=
:

> Colleagues,
>=20
> Reading draft-ietf-cdni-logging-02 Section 3.1:
>=20
>   o  Fields:
>=20
>      *  format: <field-name>[ <field-name>], where the allowed list of
>         <field-name> are specified for each Record-Type in Section 3.2
>=20
>      *  semantic: this lists the names of all the fields for which a
>         value is to appear in the CDNI Logging Records that are after
>         this directive.  The names of the fields, as well as their
>         possible occurrences, are specified for each type of CDNI
>         Logging Records in Section 3.2. The field names listed in this
>         directive MUST be separated by a whitespace (" ").
>=20
> Does this mean separated by any whitespace or specifically by a single (o=
r multiple?) space character?

How about we say that transmitting end MUST include a single spec character=
 and receiving end MUST be able to parse one or multiple space characters?


>=20
> (Section 3.2 specifies TAB MUST be used to separate the actual field valu=
es in the log)
>=20
> Thanks
> Ben
>=20
> _______________________________________________
> CDNi mailing list
> CDNi@ietf.org
> https://www.ietf.org/mailman/listinfo/cdni


From flefauch@cisco.com  Tue May 28 01:43:03 2013
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 1EB8A21F9301 for <cdni@ietfa.amsl.com>; Tue, 28 May 2013 01:43:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[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 wViDDz99xZpm for <cdni@ietfa.amsl.com>; Tue, 28 May 2013 01:42:58 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 38F1B21F855F for <cdni@ietf.org>; Tue, 28 May 2013 01:42:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1278; q=dns/txt; s=iport; t=1369730578; x=1370940178; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=hWbaFDHS3n74Irfs3RTQ/Dq37puCZTHEl0A4KQ+GQoM=; b=eCBtiH6fQ1U7P2nG0Gckr4B+oDqhkQcJvtceF7DUh6pdFe2ZIh8aYqzP yhLpNUdMjCPLNJvHWioauI3e5sycSn2pRCbnCNj1FT28eZj5hNQPY/SUO MhbWwDmr5O93a3d7axvyoCR/UMccUp/t3CjuVYpjer6x1aSWyuSFLguAl M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmwFAHdtpFGtJV2Z/2dsb2JhbABZgwgwwhKBBRZ0giMBAQEDAQEBATc0CwULAgEIIhQQJwslAgQOBQiHfwYMu3sEjmoCMQeCc2EDqHuDD4In
X-IronPort-AV: E=Sophos;i="4.87,756,1363132800"; d="scan'208";a="212645852"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-9.cisco.com with ESMTP; 28 May 2013 08:42:57 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r4S8gvPV032371 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 28 May 2013 08:42:57 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.56]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.02.0318.004; Tue, 28 May 2013 03:42:56 -0500
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Thread-Topic: [CDNi] CDNI Logging date & time
Thread-Index: AQHOW3p9RBqfEdOGEEmQYRKc7SNMApkam48A
Date: Tue, 28 May 2013 08:42:56 +0000
Message-ID: <FC236DA6F2DA77449EF2D02DF4471A8D62FB7D@xmb-rcd-x10.cisco.com>
References: <69F22737-24DE-4835-A2B5-1EAEDAA6A705@niven-jenkins.co.uk>
In-Reply-To: <69F22737-24DE-4835-A2B5-1EAEDAA6A705@niven-jenkins.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.55.161.201]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <9AFC49C3B7F02440BDA0862DD350F26D@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "cdni@ietf.org" <cdni@ietf.org>
Subject: Re: [CDNi] CDNI Logging date & time
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: Tue, 28 May 2013 08:43:03 -0000

On 28 May 2013, at 10:07, Ben Niven-Jenkins <ben@niven-jenkins.co.uk> wrote=
:

> Colleagues,
>=20
> draft-cdni-logging-02 section 3.2.1 specifies:
>=20
>   o  date:
>=20
>      *  format: <date>
>=20
>      *  semantic: the date at which the processing of request started
>         on the Surrogate.
>=20
>      *  occurrence: there MUST be one and only one instance of this
>         field.
>=20
>   o  time:
>=20
>      *  format: <time>
>=20
>      *  semantic: the time at which the processing of request started
>         on the Surrogate.
>=20
>      *  occurrence: there MUST be one and only one instance of this
>         field.
>=20
> Can we make these the end date/time instead of the start date/time?

Done. This will also be consistent with ELF.  This was an editing mistake.

Francois

>=20
> It makes the logs themselves a little easier to parse/read as the dates w=
ill be chronological rather than jumping over the place depending on start =
time/response size/etc. End date/time can still be calculated from start da=
te/time+time-taken if it is required.
>=20
> Thanks
> Ben
>=20
> _______________________________________________
> CDNi mailing list
> CDNi@ietf.org
> https://www.ietf.org/mailman/listinfo/cdni


From flefauch@cisco.com  Tue May 28 02:02:44 2013
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 0ABA221F93B9 for <cdni@ietfa.amsl.com>; Tue, 28 May 2013 02:02:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 0zt6+4zl329J for <cdni@ietfa.amsl.com>; Tue, 28 May 2013 02:02:39 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id B324721F93B7 for <cdni@ietf.org>; Tue, 28 May 2013 02:02:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7100; q=dns/txt; s=iport; t=1369731758; x=1370941358; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=+mga7EUCLjv6TQ18mhvOLsndBVutdXurldHEjZwyzsA=; b=m6Ky6RkGPa31FmTF55hgPwk9W5t/5W16Gpdjh/YseijPGiGYRtrBoEwH 1ImI4pWqUqJiDC69VVpme7D+WjwnRvki1so8aWbOCyyeIdLRprowk7p96 1hllAU7F8iunU31wrWm51qWtshAaNPNacTVwOdUBLojDrNG30bwMPW4Y0 o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmwFAKxxpFGtJV2b/2dsb2JhbABZgwgwwhKBBRZ0giQBAQQBAQFrCxACAQgiHQcnCxQRAgQOBQiIBQy7cgSObDEHgnNhA6h7gw+CJw
X-IronPort-AV: E=Sophos;i="4.87,756,1363132800";  d="scan'208,217";a="215629216"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-5.cisco.com with ESMTP; 28 May 2013 09:02:38 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r4S92cLq013113 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 28 May 2013 09:02:38 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.56]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.02.0318.004; Tue, 28 May 2013 04:02:37 -0500
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Thread-Topic: [CDNi] CDNI Logging - cs-uri
Thread-Index: AQHOW3uudsLNm27l90yND2c2v+VftJkaoQsA
Date: Tue, 28 May 2013 09:02:37 +0000
Message-ID: <FC236DA6F2DA77449EF2D02DF4471A8D62FBE4@xmb-rcd-x10.cisco.com>
References: <39F159F6-E86A-4464-AF44-C5EE7A48F8CE@niven-jenkins.co.uk>
In-Reply-To: <39F159F6-E86A-4464-AF44-C5EE7A48F8CE@niven-jenkins.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.55.161.201]
Content-Type: multipart/alternative; boundary="_000_FC236DA6F2DA77449EF2D02DF4471A8D62FBE4xmbrcdx10ciscocom_"
MIME-Version: 1.0
Cc: "cdni@ietf.org" <cdni@ietf.org>
Subject: Re: [CDNi] CDNI Logging - cs-uri
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: Tue, 28 May 2013 09:02:44 -0000

--_000_FC236DA6F2DA77449EF2D02DF4471A8D62FBE4xmbrcdx10ciscocom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


On 28 May 2013, at 10:16, Ben Niven-Jenkins <ben@niven-jenkins.co.uk<mailto=
:ben@niven-jenkins.co.uk>> wrote:

Colleagues,

draft-cdni-logging-02 section 3.2.1 states:

  o  cs-uri: [Editor's note: rename "sr-uri" ?]

     *  format: <uri>

     *  semantic: this is the absolute-URI of the request received by
        the Surrogate.  [Editor's Note: do we agree this should be an
        absolute-URI even if teh request uses a relative-URI?]

     *  occurrence: there MUST be zero or exactly one instance of this
        field.

It is cs-uri because it is the URI the User Agent presented to the surrogat=
e. sr-uri would be the URI that the surrogate presented to its upstream sou=
rce on a cache miss.

It should be the absolute URI as specified in the Request-URI (if the Reque=
st-URI includes a host) or an absolute URI constructed from the Host + Requ=
est-URI IMO.


Agreed.
I fixed the text and it now reads:


   o  cs-uri:

      *  format: <uri>

      *  semantic: this is the complete URI of the request received by
         the Surrogate.  It includes the scheme, the authority
         (regardless of whether or not it is explicitely included in the
         request-URI), the path (from the request-URI), query (when
         present in the request-URI) and fragment (when present in the
         request-URI).

      *  occurrence: there MUST be zero or exactly one instance of this
         field.

   o  ucdn-centric-uri:

      *  format: <uri>

      *  semantic: this is a complete URI derived from the complete URI
         of the request received by the Surrogate but transformed by the
         entity generating or transmitting the CDNI Logging Record, in a
         way that is agreed upon between the two ends of the CDNI
         Logging interface, so the transformed URI is meaningful to the
         uCDN.  For example, the two ends of the CDNI Logging interface
         could agree that the ucdn-centric-uri strips the part of the
         delivery-uri that exposes which individual Surrogate actually
         performed the delivery.  The details of modification performed
         to generate the ucdn-centric-uri, as well as the mechanism to
         agree on these modifications between the two sides of the CDNI
         Logging interface are outside the scope of the present
         document.  It includes the scheme, the authority, the path, and
         (when used) the query and fragment.

      *  occurrence: there MUST be one and only one instance of this
         field.


Let me know if you have additional comments.

Francois


Ben

_______________________________________________
CDNi mailing list
CDNi@ietf.org<mailto:CDNi@ietf.org>
https://www.ietf.org/mailman/listinfo/cdni


--_000_FC236DA6F2DA77449EF2D02DF4471A8D62FBE4xmbrcdx10ciscocom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <32C879ED32825E44A29623515AA01F0B@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
&nbsp;<br>
<div>
<div>On 28 May 2013, at 10:16, Ben Niven-Jenkins &lt;<a href=3D"mailto:ben@=
niven-jenkins.co.uk">ben@niven-jenkins.co.uk</a>&gt; wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">Colleagues,<br>
<br>
draft-cdni-logging-02 section 3.2.1 states:<br>
<br>
&nbsp;&nbsp;o &nbsp;cs-uri: [Editor's note: rename &quot;sr-uri&quot; ?]<br=
>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;* &nbsp;format: &lt;uri&gt;<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;* &nbsp;semantic: this is the absolute-URI of=
 the request received by<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;the Surrogate. &nbsp;[Edito=
r's Note: do we agree this should be an<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;absolute-URI even if teh re=
quest uses a relative-URI?]<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;* &nbsp;occurrence: there MUST be zero or exa=
ctly one instance of this<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;field.<br>
<br>
It is cs-uri because it is the URI the User Agent presented to the surrogat=
e. sr-uri would be the URI that the surrogate presented to its upstream sou=
rce on a cache miss.<br>
<br>
It should be the absolute URI as specified in the Request-URI (if the Reque=
st-URI includes a host) or an absolute URI constructed from the Host &#43; =
Request-URI IMO.<br>
</blockquote>
<div><br>
</div>
<div><br>
</div>
<div>Agreed.</div>
<div>I fixed the text and it now reads:</div>
<div><br>
</div>
<div>
<pre style=3D"word-wrap: break-word; white-space: pre-wrap; ">   o  cs-uri:

      *  format: &lt;uri&gt;

      *  semantic: this is the complete URI of the request received by
         the Surrogate.  It includes the scheme, the authority
         (regardless of whether or not it is explicitely included in the
         request-URI), the path (from the request-URI), query (when
         present in the request-URI) and fragment (when present in the
         request-URI).

      *  occurrence: there MUST be zero or exactly one instance of this
         field.

   o  ucdn-centric-uri:

      *  format: &lt;uri&gt;

      *  semantic: this is a complete URI derived from the complete URI
         of the request received by the Surrogate but transformed by the
         entity generating or transmitting the CDNI Logging Record, in a
         way that is agreed upon between the two ends of the CDNI
         Logging interface, so the transformed URI is meaningful to the
         uCDN.  For example, the two ends of the CDNI Logging interface
         could agree that the ucdn-centric-uri strips the part of the
         delivery-uri that exposes which individual Surrogate actually
         performed the delivery.  The details of modification performed
         to generate the ucdn-centric-uri, as well as the mechanism to
         agree on these modifications between the two sides of the CDNI
         Logging interface are outside the scope of the present
         document.  It includes the scheme, the authority, the path, and
         (when used) the query and fragment.

      *  occurrence: there MUST be one and only one instance of this
         field.
</pre>
<div><br>
</div>
<div>Let me know if you have additional comments.</div>
<div><br>
</div>
</div>
<div>Francois</div>
<br>
<blockquote type=3D"cite"><br>
Ben<br>
<br>
_______________________________________________<br>
CDNi mailing list<br>
<a href=3D"mailto:CDNi@ietf.org">CDNi@ietf.org</a><br>
https://www.ietf.org/mailman/listinfo/cdni<br>
</blockquote>
</div>
<br>
</body>
</html>

--_000_FC236DA6F2DA77449EF2D02DF4471A8D62FBE4xmbrcdx10ciscocom_--

From flefauch@cisco.com  Tue May 28 02:13:05 2013
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 D8B1221F93FB for <cdni@ietfa.amsl.com>; Tue, 28 May 2013 02:13:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 pklbNQ1b+zai for <cdni@ietfa.amsl.com>; Tue, 28 May 2013 02:13:00 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 2B74921F8900 for <cdni@ietf.org>; Tue, 28 May 2013 02:12:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1063; q=dns/txt; s=iport; t=1369732372; x=1370941972; h=from:to:cc:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=keD+EKt7aJ7KkwiM82DTDYEtlpR8egdtm4LLFsmQHCU=; b=KsvT3Su5XcM54IxFQRYAreLNuzgwlEw+jlsR/uFqX9S94vbV4RyxE5f5 V4KK7NBCdV3EuLvpmvB1/E3Kez7spUidVIW+KRigNWNMdbTcb1OUMdBcz RxrYK/pL+dvYS9DZK+gMO4FAAaH13DbspkbSfHb3DE3HxJFaNuGCwHdNr o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgoFAId0pFGtJXG+/2dsb2JhbABZgwjCQoEFFnSCJQEEOj8SARYUFEInBA4NiAW8AY5sMYJ6YQOoe4MPgic
X-IronPort-AV: E=Sophos;i="4.87,756,1363132800"; d="scan'208";a="215429703"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-1.cisco.com with ESMTP; 28 May 2013 09:12:51 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id r4S9Cp2l030673 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 28 May 2013 09:12:51 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.56]) by xhc-rcd-x04.cisco.com ([fe80::200:5efe:173.37.183.34%12]) with mapi id 14.02.0318.004; Tue, 28 May 2013 04:12:51 -0500
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: Rob Murray <RMurray@velocix.com>
Thread-Topic: CDNI Logging - ucdn-centric-uri
Thread-Index: AQHOW4OGNf9PrN7Okk6NEapp/WOwsw==
Date: Tue, 28 May 2013 09:12:50 +0000
Message-ID: <FC236DA6F2DA77449EF2D02DF4471A8D62FCC1@xmb-rcd-x10.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.55.161.201]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <E9054922B3C5C94EB25A26B8D328F0FF@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "cdni@ietf.org" <cdni@ietf.org>
Subject: [CDNi] CDNI Logging - ucdn-centric-uri
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: Tue, 28 May 2013 09:13:06 -0000

Hi Rob and all,

I've done a little more thinking about your earlier suggestion to redefine =
the ELF "r" prefix into something that designates the uCDN , and then renam=
e "ucdn-centric-uri" into "sr-uri".

I'm concluding we should not do that because:
	* this would probably actually be confusing. When reading "sr-uri" many pe=
ople will probably think this is the uri used by the dCDN surrogate to acqu=
ire the content from its upstream cache. Case in point, Ben's recent messag=
e on cs-uri precisely made that exact assumption i.e. "sr-uri would be the =
URI that the surrogate presented to its upstream source on a cache miss."=20
	* if we ever want to define an additional log field related to what happen=
s between the surrogate and its upstream cache, the natural "r" prefix will=
 be already taken.

So how about we just define new prefixes to refer to uCDN and dCDN when nee=
ded?
For example we could coin "u" for uCDN and "d" for dCDN and then we could r=
ename "ucdn-centric-uri" into "du-uri"?
Would that work?

Francois=

From ben@niven-jenkins.co.uk  Tue May 28 02:16:22 2013
Return-Path: <ben@niven-jenkins.co.uk>
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 A3EC721F90DF for <cdni@ietfa.amsl.com>; Tue, 28 May 2013 02:16:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.266
X-Spam-Level: 
X-Spam-Status: No, score=-103.266 tagged_above=-999 required=5 tests=[AWL=-0.667, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 C9sgA6ZblM+q for <cdni@ietfa.amsl.com>; Tue, 28 May 2013 02:16:17 -0700 (PDT)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.61]) by ietfa.amsl.com (Postfix) with ESMTP id 752EF21F8A0B for <cdni@ietf.org>; Tue, 28 May 2013 02:16:13 -0700 (PDT)
Received: from cpc4-cmbg17-2-0-cust814.5-4.cable.virginmedia.com ([86.14.227.47] helo=[192.168.0.4]) by mail10.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1UhG0q-0001q5-Si; Tue, 28 May 2013 10:16:13 +0100
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
In-Reply-To: <FC236DA6F2DA77449EF2D02DF4471A8D62FB5A@xmb-rcd-x10.cisco.com>
Date: Tue, 28 May 2013 10:16:11 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <798CDA4C-674C-45D2-A66C-09F12DB66811@niven-jenkins.co.uk>
References: <617086B6-30C5-457F-AF75-046E7F496035@niven-jenkins.co.uk> <FC236DA6F2DA77449EF2D02DF4471A8D62FB5A@xmb-rcd-x10.cisco.com>
To: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
X-Mailer: Apple Mail (2.1085)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Cc: "<cdni@ietf.org>" <cdni@ietf.org>
Subject: Re: [CDNi] CDNI Logging - whitespace
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: Tue, 28 May 2013 09:16:22 -0000

On 28 May 2013, at 09:39, Francois Le Faucheur (flefauch) wrote:

>=20
> On 28 May 2013, at 10:01, Ben Niven-Jenkins <ben@niven-jenkins.co.uk> =
wrote:
>=20
>> Colleagues,
>>=20
>> Reading draft-ietf-cdni-logging-02 Section 3.1:
>>=20
>>  o  Fields:
>>=20
>>     *  format: <field-name>[ <field-name>], where the allowed list of
>>        <field-name> are specified for each Record-Type in Section 3.2
>>=20
>>     *  semantic: this lists the names of all the fields for which a
>>        value is to appear in the CDNI Logging Records that are after
>>        this directive.  The names of the fields, as well as their
>>        possible occurrences, are specified for each type of CDNI
>>        Logging Records in Section 3.2. The field names listed in this
>>        directive MUST be separated by a whitespace (" ").
>>=20
>> Does this mean separated by any whitespace or specifically by a =
single (or multiple?) space character?
>=20
> How about we say that transmitting end MUST include a single spec =
character and receiving end MUST be able to parse one or multiple space =
characters?

That works for me but should we align the #Fields: directive with the =
actual log lines and use a TAB instead?

Ben

>=20
>=20
>>=20
>> (Section 3.2 specifies TAB MUST be used to separate the actual field =
values in the log)
>>=20
>> Thanks
>> Ben
>>=20
>> _______________________________________________
>> CDNi mailing list
>> CDNi@ietf.org
>> https://www.ietf.org/mailman/listinfo/cdni
>=20


From ben@niven-jenkins.co.uk  Tue May 28 02:20:44 2013
Return-Path: <ben@niven-jenkins.co.uk>
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 9121A21F9457 for <cdni@ietfa.amsl.com>; Tue, 28 May 2013 02:20:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.17
X-Spam-Level: 
X-Spam-Status: No, score=-103.17 tagged_above=-999 required=5 tests=[AWL=-0.571, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 02sdZXVRYzxz for <cdni@ietfa.amsl.com>; Tue, 28 May 2013 02:20:30 -0700 (PDT)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.61]) by ietfa.amsl.com (Postfix) with ESMTP id 81BB421F944C for <cdni@ietf.org>; Tue, 28 May 2013 02:20:29 -0700 (PDT)
Received: from cpc4-cmbg17-2-0-cust814.5-4.cable.virginmedia.com ([86.14.227.47] helo=[192.168.0.4]) by mail11.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1UhG4u-0003e6-9Z; Tue, 28 May 2013 10:20:24 +0100
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
In-Reply-To: <FC236DA6F2DA77449EF2D02DF4471A8D62FBE4@xmb-rcd-x10.cisco.com>
Date: Tue, 28 May 2013 10:20:23 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <AB10DE8B-84C2-4AF4-82B5-3B37E9256314@niven-jenkins.co.uk>
References: <39F159F6-E86A-4464-AF44-C5EE7A48F8CE@niven-jenkins.co.uk> <FC236DA6F2DA77449EF2D02DF4471A8D62FBE4@xmb-rcd-x10.cisco.com>
To: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
X-Mailer: Apple Mail (2.1085)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Cc: "cdni@ietf.org" <cdni@ietf.org>
Subject: Re: [CDNi] CDNI Logging - cs-uri
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: Tue, 28 May 2013 09:20:44 -0000

Francois,

Only comment would be that I don't think fragments are ever sent in =
Request-URIs but I suppose there's no harm in saying to log it in the =
case a User Agent erroneously sends one.

Ben

On 28 May 2013, at 10:02, Francois Le Faucheur (flefauch) wrote:

> =20
> On 28 May 2013, at 10:16, Ben Niven-Jenkins <ben@niven-jenkins.co.uk> =
wrote:
>=20
>> Colleagues,
>>=20
>> draft-cdni-logging-02 section 3.2.1 states:
>>=20
>>   o  cs-uri: [Editor's note: rename "sr-uri" ?]
>>=20
>>      *  format: <uri>
>>=20
>>      *  semantic: this is the absolute-URI of the request received by
>>         the Surrogate.  [Editor's Note: do we agree this should be an
>>         absolute-URI even if teh request uses a relative-URI?]
>>=20
>>      *  occurrence: there MUST be zero or exactly one instance of =
this
>>         field.
>>=20
>> It is cs-uri because it is the URI the User Agent presented to the =
surrogate. sr-uri would be the URI that the surrogate presented to its =
upstream source on a cache miss.
>>=20
>> It should be the absolute URI as specified in the Request-URI (if the =
Request-URI includes a host) or an absolute URI constructed from the =
Host + Request-URI IMO.
>=20
>=20
> Agreed.
> I fixed the text and it now reads:
>=20
>    o  cs-uri:
>=20
>       *  format: <uri>
>=20
>       *  semantic: this is the complete URI of the request received by
>          the Surrogate.  It includes the scheme, the authority
>          (regardless of whether or not it is explicitely included in =
the
>          request-URI), the path (from the request-URI), query (when
>          present in the request-URI) and fragment (when present in the
>          request-URI).
>=20
>       *  occurrence: there MUST be zero or exactly one instance of =
this
>          field.
>=20
>    o  ucdn-centric-uri:
>=20
>       *  format: <uri>
>=20
>       *  semantic: this is a complete URI derived from the complete =
URI
>          of the request received by the Surrogate but transformed by =
the
>          entity generating or transmitting the CDNI Logging Record, in =
a
>          way that is agreed upon between the two ends of the CDNI
>          Logging interface, so the transformed URI is meaningful to =
the
>          uCDN.  For example, the two ends of the CDNI Logging =
interface
>          could agree that the ucdn-centric-uri strips the part of the
>          delivery-uri that exposes which individual Surrogate actually
>          performed the delivery.  The details of modification =
performed
>          to generate the ucdn-centric-uri, as well as the mechanism to
>          agree on these modifications between the two sides of the =
CDNI
>          Logging interface are outside the scope of the present
>          document.  It includes the scheme, the authority, the path, =
and
>          (when used) the query and fragment.
>=20
>       *  occurrence: there MUST be one and only one instance of this
>          field.
>=20
>=20
> Let me know if you have additional comments.
>=20
> Francois
>=20
>>=20
>> Ben
>>=20
>> _______________________________________________
>> CDNi mailing list
>> CDNi@ietf.org
>> https://www.ietf.org/mailman/listinfo/cdni
>=20


From flefauch@cisco.com  Tue May 28 02:22:57 2013
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 99BDF21F86CE for <cdni@ietfa.amsl.com>; Tue, 28 May 2013 02:22:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 5m8UhQnV71F9 for <cdni@ietfa.amsl.com>; Tue, 28 May 2013 02:22:52 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 2A1BE21F8609 for <cdni@ietf.org>; Tue, 28 May 2013 02:22:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1727; q=dns/txt; s=iport; t=1369732972; x=1370942572; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=hYk3S3pqJfwPI2gI9xTop3X2BZc2a3v4LUG4qKFzrvw=; b=b3dM8n3wHVQRDdT5I4O6p+buU6lL8aiuxUIkuj9qODngD1eI94s0xyt6 aoNztXdUjmuP8396q3LqoNBJd9okxRQk60eLp68coLXKpqIQ87adzoA18 Hl6tpnQiZPlKRme8TAZdNA97kIU9v1ai/rRiWvEdFJ13YudUnDbtORexW A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmwFACB2pFGtJXG+/2dsb2JhbABZgwgwwhKBBRZ0giMBAQEDAQEBATc0CwULAgEIGAoUECcLJQIEDgUIh38GDLtzBI5qAjEHgnNhA6h7gw+CJw
X-IronPort-AV: E=Sophos;i="4.87,757,1363132800"; d="scan'208";a="215602174"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-2.cisco.com with ESMTP; 28 May 2013 09:22:51 +0000
Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id r4S9MpI1014146 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 28 May 2013 09:22:51 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.56]) by xhc-rcd-x01.cisco.com ([173.37.183.75]) with mapi id 14.02.0318.004; Tue, 28 May 2013 04:22:51 -0500
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Thread-Topic: [CDNi] CDNI Logging - whitespace
Thread-Index: AQHOW3nFR8FSDAmDH0ib1NZiSkcA6JkamrSAgAAKJ4CAAAHbAA==
Date: Tue, 28 May 2013 09:22:51 +0000
Message-ID: <FC236DA6F2DA77449EF2D02DF4471A8D62FD5B@xmb-rcd-x10.cisco.com>
References: <617086B6-30C5-457F-AF75-046E7F496035@niven-jenkins.co.uk> <FC236DA6F2DA77449EF2D02DF4471A8D62FB5A@xmb-rcd-x10.cisco.com> <798CDA4C-674C-45D2-A66C-09F12DB66811@niven-jenkins.co.uk>
In-Reply-To: <798CDA4C-674C-45D2-A66C-09F12DB66811@niven-jenkins.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.55.161.201]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <D9D066FADFDA8A42B0F97CE5ACC8D087@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "cdni@ietf.org" <cdni@ietf.org>
Subject: Re: [CDNi] CDNI Logging - whitespace
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: Tue, 28 May 2013 09:22:57 -0000

On 28 May 2013, at 11:16, Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
 wrote:

>=20
> On 28 May 2013, at 09:39, Francois Le Faucheur (flefauch) wrote:
>=20
>>=20
>> On 28 May 2013, at 10:01, Ben Niven-Jenkins <ben@niven-jenkins.co.uk> wr=
ote:
>>=20
>>> Colleagues,
>>>=20
>>> Reading draft-ietf-cdni-logging-02 Section 3.1:
>>>=20
>>> o  Fields:
>>>=20
>>>    *  format: <field-name>[ <field-name>], where the allowed list of
>>>       <field-name> are specified for each Record-Type in Section 3.2
>>>=20
>>>    *  semantic: this lists the names of all the fields for which a
>>>       value is to appear in the CDNI Logging Records that are after
>>>       this directive.  The names of the fields, as well as their
>>>       possible occurrences, are specified for each type of CDNI
>>>       Logging Records in Section 3.2. The field names listed in this
>>>       directive MUST be separated by a whitespace (" ").
>>>=20
>>> Does this mean separated by any whitespace or specifically by a single =
(or multiple?) space character?
>>=20
>> How about we say that transmitting end MUST include a single spec charac=
ter and receiving end MUST be able to parse one or multiple space character=
s?
>=20
> That works for me but should we align the #Fields: directive with the act=
ual log lines and use a TAB instead

Makes sense. I have changed it to TAB.



> Ben
>=20
>>=20
>>=20
>>>=20
>>> (Section 3.2 specifies TAB MUST be used to separate the actual field va=
lues in the log)
>>>=20
>>> Thanks
>>> Ben
>>>=20
>>> _______________________________________________
>>> CDNi mailing list
>>> CDNi@ietf.org
>>> https://www.ietf.org/mailman/listinfo/cdni
>>=20
>=20


From flefauch@cisco.com  Tue May 28 02:40:28 2013
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 AC22721F955C for <cdni@ietfa.amsl.com>; Tue, 28 May 2013 02:40:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 lCGBuXqFfK3h for <cdni@ietfa.amsl.com>; Tue, 28 May 2013 02:40:23 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id AEC7821F955E for <cdni@ietf.org>; Tue, 28 May 2013 02:40:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5173; q=dns/txt; s=iport; t=1369734023; x=1370943623; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=BFIRqOXmBHhRSv9uttVwAIk2ap8WKx7Suk0/ALAWEdY=; b=UVjNPAMqYfyakX66oyMVcH3lTGLdIV6j6L1QZDXg5IQ+U8YDWLrwgikQ SlC5/mgy/EEeEJ5FG7FQ9+TTIUFhiZIRyF8a8JyDYtDFJQ09La31ypv/m E7BU2pxB4czi3vk2FUxA4LiiD4+bMp44zWUfoQzIjHqqtg/3JjhBUD0/8 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmwFAJl6pFGtJXHB/2dsb2JhbABZgwgwwhKBBRZ0giMBAQEDAQEBATc0CwULAgEIGAoUECcLJQIEDgUIh38GDLtqBI5qAjEHgnNhA6h7gw+CJw
X-IronPort-AV: E=Sophos;i="4.87,757,1363132800"; d="scan'208";a="215437644"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-1.cisco.com with ESMTP; 28 May 2013 09:40:23 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r4S9eNtC006663 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 28 May 2013 09:40:23 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.56]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.02.0318.004; Tue, 28 May 2013 04:40:23 -0500
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Thread-Topic: [CDNi] CDNI Logging - cs-uri
Thread-Index: AQHOW3uudsLNm27l90yND2c2v+VftJkaoQsAgAAE+ICAAAWUgA==
Date: Tue, 28 May 2013 09:40:22 +0000
Message-ID: <FC236DA6F2DA77449EF2D02DF4471A8D62FDEC@xmb-rcd-x10.cisco.com>
References: <39F159F6-E86A-4464-AF44-C5EE7A48F8CE@niven-jenkins.co.uk> <FC236DA6F2DA77449EF2D02DF4471A8D62FBE4@xmb-rcd-x10.cisco.com> <AB10DE8B-84C2-4AF4-82B5-3B37E9256314@niven-jenkins.co.uk>
In-Reply-To: <AB10DE8B-84C2-4AF4-82B5-3B37E9256314@niven-jenkins.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.55.161.201]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <C141124B9C878D49AC00F31694856F8F@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "cdni@ietf.org" <cdni@ietf.org>
Subject: Re: [CDNi] CDNI Logging - cs-uri
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: Tue, 28 May 2013 09:40:28 -0000

On 28 May 2013, at 11:20, Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
 wrote:

> Francois,
>=20
> Only comment would be that I don't think fragments are ever sent in Reque=
st-URIs

Good point.

> but I suppose there's no harm in saying to log it in the case a User Agen=
t erroneously sends one.

This makes me realise that I was more or less re-defining a "http_URL" , wh=
ich is actually perfectly well defined already in section 3.2.2 of RFC2616:
"
http_URL =3D "http:" "//" host [ ":" port ] [ abs_path [ "?" query ]]
"
So what I've done is add an explicit reference to that definition. I think =
this makes it brief and non-ambigous. So it now reads:

"
   o  cs-uri:

      *  format: <uri>

      *  semantic: this is the complete http_URL (as specified in
         [RFC2616]) of the request received by the Surrogate.

      *  occurrence: there MUST be zero or exactly one instance of this
         field.

   o  ucdn-centric-uri:

      *  format: <uri>

      *  semantic: this is a complete http_URL (as specified in
         [RFC2616]) derived from the complete URI of the request
         received by the Surrogate but transformed by the entity
         generating or transmitting the CDNI Logging Record, in a way
         that is agreed upon between the two ends of the CDNI Logging
         interface, so the transformed URI is meaningful to the uCDN.
         For example, the two ends of the CDNI Logging interface could
         agree that the ucdn-centric-uri strips the part of the
         delivery-uri that exposes which individual Surrogate actually
         performed the delivery.  The details of modification performed
         to generate the ucdn-centric-uri, as well as the mechanism to
         agree on these modifications between the two sides of the CDNI
         Logging interface are outside the scope of the present
         document.

      *  occurrence: there MUST be one and only one instance of this
         field.

"

All good?

Francois


>=20
> Ben
>=20
> On 28 May 2013, at 10:02, Francois Le Faucheur (flefauch) wrote:
>=20
>>=20
>> On 28 May 2013, at 10:16, Ben Niven-Jenkins <ben@niven-jenkins.co.uk> wr=
ote:
>>=20
>>> Colleagues,
>>>=20
>>> draft-cdni-logging-02 section 3.2.1 states:
>>>=20
>>>  o  cs-uri: [Editor's note: rename "sr-uri" ?]
>>>=20
>>>     *  format: <uri>
>>>=20
>>>     *  semantic: this is the absolute-URI of the request received by
>>>        the Surrogate.  [Editor's Note: do we agree this should be an
>>>        absolute-URI even if teh request uses a relative-URI?]
>>>=20
>>>     *  occurrence: there MUST be zero or exactly one instance of this
>>>        field.
>>>=20
>>> It is cs-uri because it is the URI the User Agent presented to the surr=
ogate. sr-uri would be the URI that the surrogate presented to its upstream=
 source on a cache miss.
>>>=20
>>> It should be the absolute URI as specified in the Request-URI (if the R=
equest-URI includes a host) or an absolute URI constructed from the Host + =
Request-URI IMO.
>>=20
>>=20
>> Agreed.
>> I fixed the text and it now reads:
>>=20
>>   o  cs-uri:
>>=20
>>      *  format: <uri>
>>=20
>>      *  semantic: this is the complete URI of the request received by
>>         the Surrogate.  It includes the scheme, the authority
>>         (regardless of whether or not it is explicitely included in the
>>         request-URI), the path (from the request-URI), query (when
>>         present in the request-URI) and fragment (when present in the
>>         request-URI).
>>=20
>>      *  occurrence: there MUST be zero or exactly one instance of this
>>         field.
>>=20
>>   o  ucdn-centric-uri:
>>=20
>>      *  format: <uri>
>>=20
>>      *  semantic: this is a complete URI derived from the complete URI
>>         of the request received by the Surrogate but transformed by the
>>         entity generating or transmitting the CDNI Logging Record, in a
>>         way that is agreed upon between the two ends of the CDNI
>>         Logging interface, so the transformed URI is meaningful to the
>>         uCDN.  For example, the two ends of the CDNI Logging interface
>>         could agree that the ucdn-centric-uri strips the part of the
>>         delivery-uri that exposes which individual Surrogate actually
>>         performed the delivery.  The details of modification performed
>>         to generate the ucdn-centric-uri, as well as the mechanism to
>>         agree on these modifications between the two sides of the CDNI
>>         Logging interface are outside the scope of the present
>>         document.  It includes the scheme, the authority, the path, and
>>         (when used) the query and fragment.
>>=20
>>      *  occurrence: there MUST be one and only one instance of this
>>         field.
>>=20
>>=20
>> Let me know if you have additional comments.
>>=20
>> Francois
>>=20
>>>=20
>>> Ben
>>>=20
>>> _______________________________________________
>>> CDNi mailing list
>>> CDNi@ietf.org
>>> https://www.ietf.org/mailman/listinfo/cdni
>>=20
>=20


From ben@niven-jenkins.co.uk  Tue May 28 02:49:58 2013
Return-Path: <ben@niven-jenkins.co.uk>
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 2F9E021F9605 for <cdni@ietfa.amsl.com>; Tue, 28 May 2013 02:49:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 X4YXN+4Enp6D for <cdni@ietfa.amsl.com>; Tue, 28 May 2013 02:49:53 -0700 (PDT)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.62]) by ietfa.amsl.com (Postfix) with ESMTP id 36FA321F9600 for <cdni@ietf.org>; Tue, 28 May 2013 02:49:53 -0700 (PDT)
Received: from host4.velocix.com ([81.134.152.4] helo=xxx.corp.velocix.com) by mail5.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1UhGXQ-0000qW-0z; Tue, 28 May 2013 10:49:52 +0100
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
In-Reply-To: <FC236DA6F2DA77449EF2D02DF4471A8D62FDEC@xmb-rcd-x10.cisco.com>
Date: Tue, 28 May 2013 10:49:49 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <47225FB6-C8EE-418D-8506-C0E44D4643AB@niven-jenkins.co.uk>
References: <39F159F6-E86A-4464-AF44-C5EE7A48F8CE@niven-jenkins.co.uk> <FC236DA6F2DA77449EF2D02DF4471A8D62FBE4@xmb-rcd-x10.cisco.com> <AB10DE8B-84C2-4AF4-82B5-3B37E9256314@niven-jenkins.co.uk> <FC236DA6F2DA77449EF2D02DF4471A8D62FDEC@xmb-rcd-x10.cisco.com>
To: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
X-Mailer: Apple Mail (2.1085)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Cc: "cdni@ietf.org" <cdni@ietf.org>
Subject: Re: [CDNi] CDNI Logging - cs-uri
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: Tue, 28 May 2013 09:49:58 -0000

works for me. Ben

On 28 May 2013, at 10:40, Francois Le Faucheur (flefauch) wrote:

>=20
> On 28 May 2013, at 11:20, Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
> wrote:
>=20
>> Francois,
>>=20
>> Only comment would be that I don't think fragments are ever sent in =
Request-URIs
>=20
> Good point.
>=20
>> but I suppose there's no harm in saying to log it in the case a User =
Agent erroneously sends one.
>=20
> This makes me realise that I was more or less re-defining a "http_URL" =
, which is actually perfectly well defined already in section 3.2.2 of =
RFC2616:
> "
> http_URL =3D "http:" "//" host [ ":" port ] [ abs_path [ "?" query ]]
> "
> So what I've done is add an explicit reference to that definition. I =
think this makes it brief and non-ambigous. So it now reads:
>=20
> "
>   o  cs-uri:
>=20
>      *  format: <uri>
>=20
>      *  semantic: this is the complete http_URL (as specified in
>         [RFC2616]) of the request received by the Surrogate.
>=20
>      *  occurrence: there MUST be zero or exactly one instance of this
>         field.
>=20
>   o  ucdn-centric-uri:
>=20
>      *  format: <uri>
>=20
>      *  semantic: this is a complete http_URL (as specified in
>         [RFC2616]) derived from the complete URI of the request
>         received by the Surrogate but transformed by the entity
>         generating or transmitting the CDNI Logging Record, in a way
>         that is agreed upon between the two ends of the CDNI Logging
>         interface, so the transformed URI is meaningful to the uCDN.
>         For example, the two ends of the CDNI Logging interface could
>         agree that the ucdn-centric-uri strips the part of the
>         delivery-uri that exposes which individual Surrogate actually
>         performed the delivery.  The details of modification performed
>         to generate the ucdn-centric-uri, as well as the mechanism to
>         agree on these modifications between the two sides of the CDNI
>         Logging interface are outside the scope of the present
>         document.
>=20
>      *  occurrence: there MUST be one and only one instance of this
>         field.
>=20
> "
>=20
> All good?
>=20
> Francois
>=20
>=20
>>=20
>> Ben
>>=20
>> On 28 May 2013, at 10:02, Francois Le Faucheur (flefauch) wrote:
>>=20
>>>=20
>>> On 28 May 2013, at 10:16, Ben Niven-Jenkins =
<ben@niven-jenkins.co.uk> wrote:
>>>=20
>>>> Colleagues,
>>>>=20
>>>> draft-cdni-logging-02 section 3.2.1 states:
>>>>=20
>>>> o  cs-uri: [Editor's note: rename "sr-uri" ?]
>>>>=20
>>>>    *  format: <uri>
>>>>=20
>>>>    *  semantic: this is the absolute-URI of the request received by
>>>>       the Surrogate.  [Editor's Note: do we agree this should be an
>>>>       absolute-URI even if teh request uses a relative-URI?]
>>>>=20
>>>>    *  occurrence: there MUST be zero or exactly one instance of =
this
>>>>       field.
>>>>=20
>>>> It is cs-uri because it is the URI the User Agent presented to the =
surrogate. sr-uri would be the URI that the surrogate presented to its =
upstream source on a cache miss.
>>>>=20
>>>> It should be the absolute URI as specified in the Request-URI (if =
the Request-URI includes a host) or an absolute URI constructed from the =
Host + Request-URI IMO.
>>>=20
>>>=20
>>> Agreed.
>>> I fixed the text and it now reads:
>>>=20
>>>  o  cs-uri:
>>>=20
>>>     *  format: <uri>
>>>=20
>>>     *  semantic: this is the complete URI of the request received by
>>>        the Surrogate.  It includes the scheme, the authority
>>>        (regardless of whether or not it is explicitely included in =
the
>>>        request-URI), the path (from the request-URI), query (when
>>>        present in the request-URI) and fragment (when present in the
>>>        request-URI).
>>>=20
>>>     *  occurrence: there MUST be zero or exactly one instance of =
this
>>>        field.
>>>=20
>>>  o  ucdn-centric-uri:
>>>=20
>>>     *  format: <uri>
>>>=20
>>>     *  semantic: this is a complete URI derived from the complete =
URI
>>>        of the request received by the Surrogate but transformed by =
the
>>>        entity generating or transmitting the CDNI Logging Record, in =
a
>>>        way that is agreed upon between the two ends of the CDNI
>>>        Logging interface, so the transformed URI is meaningful to =
the
>>>        uCDN.  For example, the two ends of the CDNI Logging =
interface
>>>        could agree that the ucdn-centric-uri strips the part of the
>>>        delivery-uri that exposes which individual Surrogate actually
>>>        performed the delivery.  The details of modification =
performed
>>>        to generate the ucdn-centric-uri, as well as the mechanism to
>>>        agree on these modifications between the two sides of the =
CDNI
>>>        Logging interface are outside the scope of the present
>>>        document.  It includes the scheme, the authority, the path, =
and
>>>        (when used) the query and fragment.
>>>=20
>>>     *  occurrence: there MUST be one and only one instance of this
>>>        field.
>>>=20
>>>=20
>>> Let me know if you have additional comments.
>>>=20
>>> Francois
>>>=20
>>>>=20
>>>> Ben
>>>>=20
>>>> _______________________________________________
>>>> CDNi mailing list
>>>> CDNi@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/cdni
>>>=20
>>=20
>=20


From kleung@cisco.com  Tue May 28 11:26:11 2013
Return-Path: <kleung@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 5A26E11E80E0 for <cdni@ietfa.amsl.com>; Tue, 28 May 2013 11:26:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 PFkNx+SaVkqB for <cdni@ietfa.amsl.com>; Tue, 28 May 2013 11:26:05 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id D318021F8F33 for <cdni@ietf.org>; Tue, 28 May 2013 11:26:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=21926; q=dns/txt; s=iport; t=1369765561; x=1370975161; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=/euOKUCgHgk/V3hZOvh/KoaUdHKNYWlPJO+yChKg6wg=; b=k9zy502jFwr+CCW4EO4WhLbzQMuFO89OyLunnU4L+UzMqlTIJYuYFGi7 jUCx/kt7uZD+pH3GunMnHzLaJ7flgkq6hCYDvSVcJmjc/SOb20q7wR6Th cEVmaFDwUAqf/w2hijXEPgobxxxO2bIFVcb8KPfZjwb3oXvk6eWjyCOwK U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlIGAI71pFGtJXG8/2dsb2JhbABZgkREMMIbgQcWdIIjAQEBBC1DCRACAQgOAwQBAQsWBwcyFAkIAgQBDQUIE4dyvHuObDEGAYJzYQOTapURgw+BaiQZ
X-IronPort-AV: E=Sophos;i="4.87,759,1363132800";  d="scan'208,217";a="215851074"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-8.cisco.com with ESMTP; 28 May 2013 18:26:00 +0000
Received: from xhc-aln-x12.cisco.com (xhc-aln-x12.cisco.com [173.36.12.86]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id r4SIPxnb000791 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 28 May 2013 18:25:59 GMT
Received: from xmb-aln-x03.cisco.com ([169.254.6.219]) by xhc-aln-x12.cisco.com ([173.36.12.86]) with mapi id 14.02.0318.004; Tue, 28 May 2013 13:25:59 -0500
From: "Kent Leung (kleung)" <kleung@cisco.com>
To: Daryl Malas <D.Malas@cablelabs.com>, "yiu_lee@cable.comcast.com" <yiu_lee@cable.comcast.com>
Thread-Topic: [CDNi] Chair review of Requirements draft
Thread-Index: AQHOWL4ol8g/hXc8EEqlADDdC7rE15ka79/w
Date: Tue, 28 May 2013 18:25:59 +0000
Message-ID: <CD85F32117029D4F9AEF48BDEF5536AB10265446@xmb-aln-x03.cisco.com>
References: <CDC52B13.C1C6%d.malas@cablelabs.com>
In-Reply-To: <CDC52B13.C1C6%d.malas@cablelabs.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.127.1]
Content-Type: multipart/alternative; boundary="_000_CD85F32117029D4F9AEF48BDEF5536AB10265446xmbalnx03ciscoc_"
MIME-Version: 1.0
Cc: "cdni@ietf.org" <cdni@ietf.org>
Subject: Re: [CDNi] Chair review of Requirements draft
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: Tue, 28 May 2013 18:26:11 -0000

--_000_CD85F32117029D4F9AEF48BDEF5536AB10265446xmbalnx03ciscoc_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Daryl. Thanks for your thorough review. We should be able to incorporate=
 your comments into the next version in a few days.

Kent

From: Daryl Malas [mailto:D.Malas@cablelabs.com]
Sent: Friday, May 24, 2013 1:35 PM
To: Kent Leung (kleung); yiu_lee@cable.comcast.com
Cc: cdni@ietf.org
Subject: [CDNi] Chair review of Requirements draft

Kent and Yiu,

Here is my chair review of the requirements draft.  Overall, I think this d=
raft is in great shape.  Let me know if you have any questions.

Regards,

Daryl

Abstract:
I think the cdni WG charter actually describes the problem better than the =
text used in the draft.  I recommend better aligning with the charter text =
- "As a result of the significant growth in content delivered over IP netwo=
rks, existing CDN providers are scaling up their infrastructure and many Ne=
twork Service Providers and Enterprise Service Providers are deploying thei=
r own CDNs. Subject to the policy of the CSP, it is generally desirable tha=
t a given item of content can be delivered to an end user regardless of tha=
t end user's location or attachment network.  This creates a need for inter=
connecting (previously) standalone CDNs so they can interoperate and collec=
tively behave as a single delivery infrastructure."

Nit - "...such CDN interconnection." to "...such CDN interconnections."

Remove this sentence - "This draft is a work in progress and requirements m=
ay be added, modified, or removed by the working group."

The "Requirements Language" should be moved to the "Terminology" section.

Under the sub-bullets for "high, medium and low," I recommend we remove ref=
erences to compromising the working group's schedule.  Instead, change thes=
e comments to indicate the goal in assigning the varying priorities is rela=
tive to providing a "deployable solution in a short timeframe (18-24 months=
) as needed by the industry."  This is the goal as part of the working grou=
p charter.

Introduction:
My experience is that "subjective" language should be avoided in IETF draft=
s.  The introduction in this draft is full of subjective phrases: "rapidly =
increasing and expected to continue", "reduced delivery cost", "improved qu=
ality of experience", "increased robustness", "cost benefit and user experi=
ence".  At a minimum, I suggest removing some of this subjectivity and focu=
s on how CDNI will allow for content delivery across multiple CDNs.

In the last paragraph, instead of saying "In order to meet the timelines" -=
- see comment above regarding "short timeframe (18-24 months) as needed by =
the industry."

CDNI Control Interface Requirements:
The following sentence lends to discussing potential solutions.  "We observ=
e that while the CDNI Control interface is currently discussed as a single =
"protocol", further analysis will determine whether the corresponding requi=
rements are to be realized over a single interface and protocol, or over mu=
ltiple interfaces and protocols."  I suggest we remove this from this requi=
rement and make a statement at the beginning along the lines of, "The worki=
ng group attempted to align requirements with the appropriate interface; ho=
wever, solutions to these requirements may apply to a different interface o=
r another interface in addition to the interface it is associated with."

CI-1 - Suggest changing this requirement from "...Downstream CDN (and, if c=
ascaded CDNs are supported by the solution, that the potential cascaded Dow=
nstream CDNs) delete..." to "...Downstream CDN, including downstream cascad=
ed CDNs, delete..."  Apply this to CI-3, CI-4 and any other similar referen=
ces.  Since, we support cascaded CDNs, then we should simply specify the in=
clusion in the requirement.

CI-4 - I think we should require a "reason" to be included with a failure r=
esponse.  Initially it could simply be a string, unless we are going to sim=
ply use HTTP response codes.

CI-8 - "CDNI interconnection" is redundant.  Also, I think "i.e." should be=
 "e.g.".

CDNI Request Routing/Redirection Interface Requirements:
RI-6 appears to be what RI-5 refers to with regards to the "loop prevention=
 mechanism".  If this is the case, I think we should add that language to R=
I-6 and change the order of these two.

CDNI Metadata Distribution Interface Requirements:
MI-16 has a list with only 1 bullet point.  I suggest changing it to, "For =
example, this could potentially including the need to validate URI signed i=
nformation (e.g.  Expiry time, Client IP address)."
MI-21 nit, "Streamin" to "Streaming"; and, this needs to be removed and add=
ressed "[Ed: need to improve wording?]"

CDNI Logging Interface Requirements:
[Same comment as in the CDNI Control Interface Requirements with regards to=
 noting whether it may or may not be multiple protocols.]
LI-13 nit, "requests on via the CDNI" to "requests via the CDNI"

CDNI Security Requirements:
Opening paragraph nit, "Some of those" to "Some of these".

>end.

--_000_CD85F32117029D4F9AEF48BDEF5536AB10265446xmbalnx03ciscoc_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi Daryl. Thanks for your=
 thorough review. We should be able to incorporate your comments into the n=
ext version in a few days.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Kent<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Daryl Ma=
las [mailto:D.Malas@cablelabs.com]
<br>
<b>Sent:</b> Friday, May 24, 2013 1:35 PM<br>
<b>To:</b> Kent Leung (kleung); yiu_lee@cable.comcast.com<br>
<b>Cc:</b> cdni@ietf.org<br>
<b>Subject:</b> [CDNi] Chair review of Requirements draft<o:p></o:p></span>=
</p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">Kent and Yiu,<o:p></o:p></s=
pan></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">Here is my chair review of =
the requirements draft. &nbsp;Overall, I think this draft is in great shape=
. &nbsp;Let me know if you have any questions.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">Regards,<o:p></o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">Daryl<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">Abstract:<o:p></o:p></span>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">I think the cdni WG charter=
 actually describes the problem better than the text used in the draft. &nb=
sp;I recommend better aligning with the charter text - &quot;As a
 result of the significant growth in content delivered over IP&nbsp;network=
s, existing CDN providers are scaling up their infrastructure and&nbsp;many=
 Network Service Providers and Enterprise Service Providers are&nbsp;deploy=
ing their own CDNs. Subject to the policy of the
 CSP, it is&nbsp;generally desirable that a given item of content can be de=
livered to an&nbsp;end user regardless of that end user's location or attac=
hment network. &nbsp;This creates a need for interconnecting (previously) s=
tandalone CDNs so&nbsp;they can interoperate and collectively
 behave as a single delivery&nbsp;infrastructure.&quot;<o:p></o:p></span></=
p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">Nit - &quot;&#8230;such CDN=
 interconnection.&quot; to &quot;&#8230;such CDN interconnections.&quot;<o:=
p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">Remove this sentence - &quo=
t;This draft is a work in progress and requirements may be&nbsp;added, modi=
fied, or removed by the working group.&quot;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">The &quot;Requirements Lang=
uage&quot; should be moved to the &quot;Terminology&quot; section.<o:p></o:=
p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">Under the sub-bullets for &=
quot;high, medium and low,&quot; I recommend we remove references to compro=
mising the working group's schedule. &nbsp;Instead, change these comments
 to indicate the goal in assigning the varying priorities is relative to pr=
oviding a &quot;deployable solution in a short timeframe (18-24 months) as&=
nbsp;needed by the industry.&quot; &nbsp;This is the goal as part of the wo=
rking group charter.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">Introduction:<o:p></o:p></s=
pan></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">My experience is that &quot=
;subjective&quot; language should be avoided in IETF drafts. &nbsp;The intr=
oduction in this draft is full of subjective phrases: &quot;rapidly increas=
ing
 and expected to continue&quot;, &quot;reduced delivery cost&quot;, &quot;i=
mproved quality of experience&quot;, &quot;increased&nbsp;robustness&quot;,=
 &quot;cost&nbsp;benefit and user experience&quot;. &nbsp;At a minimum, I s=
uggest removing some of this subjectivity and focus on how CDNI will allow =
for content delivery
 across multiple CDNs.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">In the last paragraph, inst=
ead of saying &quot;In order to meet the timelines&quot; -- see comment abo=
ve regarding &quot;short timeframe (18-24 months) as needed by the industry=
.&quot;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">CDNI Control Interface Requ=
irements:<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">The following sentence lend=
s to discussing potential solutions. &nbsp;&quot;We observe that while the =
CDNI Control interface is&nbsp;currently discussed as a single &quot;protoc=
ol&quot;,
 further analysis will&nbsp;determine whether the corresponding requirement=
s are to be realized&nbsp;over a single interface and protocol, or over mul=
tiple interfaces and&nbsp;protocols.&quot; &nbsp;I suggest we remove this f=
rom this requirement and make a statement at the beginning
 along the lines of, &quot;The working group attempted to align requirement=
s with the appropriate interface; however, solutions to these requirements =
may apply to a different interface or another interface in addition to the =
interface it is associated with.&quot;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">CI-1 &#8211; Suggest changi=
ng this requirement from &quot;&#8230;Downstream CDN (and, if cascaded CDNs=
 are&nbsp;supported by the solution, that the potential cascaded&nbsp;Downs=
tream CDNs)
 delete&#8230;&quot; to &quot;&#8230;Downstream CDN, including downstream c=
ascaded CDNs, delete&#8230;&quot; &nbsp;Apply this to CI-3, CI-4 and any ot=
her similar references. &nbsp;Since, we support cascaded CDNs, then we shou=
ld simply specify the inclusion in the requirement.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">CI-4 &#8211; I think we sho=
uld require a &quot;reason&quot; to be included with a failure response. &n=
bsp;Initially it could simply be a string, unless we are going to simply us=
e
 HTTP response codes.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">CI-8 - &quot;CDNI&nbsp;inte=
rconnection&quot; is redundant. &nbsp;Also, I think &quot;i.e.&quot; should=
 be &quot;e.g.&quot;.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">CDNI Request Routing/Redire=
ction Interface Requirements:<o:p></o:p></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">RI-6 appears to be what RI-=
5 refers to with regards to the &quot;loop prevention&nbsp;mechanism&quot;.=
 &nbsp;If this is the case, I think we should add that language to RI-6 and
 change the order of these two.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">CDNI Metadata Distribution =
Interface Requirements:<o:p></o:p></span></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">MI-16 has a list with only =
1 bullet point. &nbsp;I&nbsp;suggest changing it to, &quot;For example,&nbs=
p;this could potentially including the&nbsp;need to validate URI signed inf=
ormation
 (e.g. &nbsp;Expiry&nbsp;time, Client IP address).&quot;<o:p></o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">MI-21 nit, &quot;Streamin&q=
uot; to &quot;Streaming&quot;; and, this needs to be removed and addressed =
&quot;[Ed: need&nbsp;to improve wording?]&quot;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">CDNI Logging Interface Requ=
irements:<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">[Same comment as in the CDN=
I Control Interface Requirements with regards to noting whether it may or m=
ay not be multiple protocols.]<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">LI-13 nit, &quot;requests o=
n via the CDNI&quot; to &quot;requests via the CDNI&quot;<o:p></o:p></span>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">CDNI Security Requirements:=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">Opening paragraph nit, &quo=
t;Some of those&quot; to &quot;Some of these&quot;.<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">&gt;end.<o:p></o:p></span><=
/p>
</div>
</div>
</body>
</html>

--_000_CD85F32117029D4F9AEF48BDEF5536AB10265446xmbalnx03ciscoc_--

From D.Malas@cablelabs.com  Tue May 28 12:47:53 2013
Return-Path: <D.Malas@cablelabs.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 7AFBA11E80D5 for <cdni@ietfa.amsl.com>; Tue, 28 May 2013 12:47:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.462
X-Spam-Level: 
X-Spam-Status: No, score=-100.462 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
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 yHSoXWUDhEjv for <cdni@ietfa.amsl.com>; Tue, 28 May 2013 12:47:48 -0700 (PDT)
Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by ietfa.amsl.com (Postfix) with ESMTP id 292D911E80F9 for <cdni@ietf.org>; Tue, 28 May 2013 12:47:47 -0700 (PDT)
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.5/8.14.5) with ESMTP id r4SJljrO002601; Tue, 28 May 2013 13:47:45 -0600
Received: from exchange.cablelabs.com (10.5.0.19) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/407/kyzyl.cablelabs.com); Tue, 28 May 2013 13:47:45 -0600 (MDT)
X-Virus-Status: clean(F-Secure/fsigk_smtp/407/kyzyl.cablelabs.com)
Received: from EXCHANGE.cablelabs.com ([fe80::797a:96d1:3c53:18ee]) by EXCHANGE.cablelabs.com ([fe80::797a:96d1:3c53:18ee%11]) with mapi id 14.03.0123.003; Tue, 28 May 2013 13:47:45 -0600
From: Daryl Malas <D.Malas@cablelabs.com>
To: "Kent Leung (kleung)" <kleung@cisco.com>, "yiu_lee@cable.comcast.com" <yiu_lee@cable.comcast.com>
Thread-Topic: [CDNi] Chair review of Requirements draft
Thread-Index: AQHOWL4ol8g/hXc8EEqlADDdC7rE15ka79/wgAAXFQA=
Date: Tue, 28 May 2013 19:47:45 +0000
Message-ID: <CDCA65A1.C263%d.malas@cablelabs.com>
In-Reply-To: <CD85F32117029D4F9AEF48BDEF5536AB10265446@xmb-aln-x03.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.4.130416
x-originating-ip: [10.5.0.27]
Content-Type: multipart/alternative; boundary="_000_CDCA65A1C263dmalascablelabscom_"
MIME-Version: 1.0
X-Approved: ondar
Cc: "cdni@ietf.org" <cdni@ietf.org>
Subject: Re: [CDNi] Chair review of Requirements draft
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: Tue, 28 May 2013 19:47:53 -0000

--_000_CDCA65A1C263dmalascablelabscom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Kent,

Thanks for your (and Yiu) efforts.  Once we have the final revision, I will=
 start the process of submitting it for AD review.  I will be the document =
shepherd on this draft, also.

Regards,

Daryl

From: "Kent Leung (kleung)" <kleung@cisco.com<mailto:kleung@cisco.com>>
Date: Tuesday, May 28, 2013 12:25 PM
To: Daryl Malas <d.malas@cablelabs.com<mailto:d.malas@cablelabs.com>>, "yiu=
_lee@cable.comcast.com<mailto:yiu_lee@cable.comcast.com>" <yiu_lee@cable.co=
mcast.com<mailto:yiu_lee@cable.comcast.com>>
Cc: "cdni@ietf.org<mailto:cdni@ietf.org>" <cdni@ietf.org<mailto:cdni@ietf.o=
rg>>
Subject: RE: [CDNi] Chair review of Requirements draft

Hi Daryl. Thanks for your thorough review. We should be able to incorporate=
 your comments into the next version in a few days.

Kent

From: Daryl Malas [mailto:D.Malas@cablelabs.com]
Sent: Friday, May 24, 2013 1:35 PM
To: Kent Leung (kleung); yiu_lee@cable.comcast.com<mailto:yiu_lee@cable.com=
cast.com>
Cc: cdni@ietf.org<mailto:cdni@ietf.org>
Subject: [CDNi] Chair review of Requirements draft

Kent and Yiu,

Here is my chair review of the requirements draft.  Overall, I think this d=
raft is in great shape.  Let me know if you have any questions.

Regards,

Daryl

Abstract:
I think the cdni WG charter actually describes the problem better than the =
text used in the draft.  I recommend better aligning with the charter text =
- "As a result of the significant growth in content delivered over IP netwo=
rks, existing CDN providers are scaling up their infrastructure and many Ne=
twork Service Providers and Enterprise Service Providers are deploying thei=
r own CDNs. Subject to the policy of the CSP, it is generally desirable tha=
t a given item of content can be delivered to an end user regardless of tha=
t end user's location or attachment network.  This creates a need for inter=
connecting (previously) standalone CDNs so they can interoperate and collec=
tively behave as a single delivery infrastructure."

Nit - "=85such CDN interconnection." to "=85such CDN interconnections."

Remove this sentence - "This draft is a work in progress and requirements m=
ay be added, modified, or removed by the working group."

The "Requirements Language" should be moved to the "Terminology" section.

Under the sub-bullets for "high, medium and low," I recommend we remove ref=
erences to compromising the working group's schedule.  Instead, change thes=
e comments to indicate the goal in assigning the varying priorities is rela=
tive to providing a "deployable solution in a short timeframe (18-24 months=
) as needed by the industry."  This is the goal as part of the working grou=
p charter.

Introduction:
My experience is that "subjective" language should be avoided in IETF draft=
s.  The introduction in this draft is full of subjective phrases: "rapidly =
increasing and expected to continue", "reduced delivery cost", "improved qu=
ality of experience", "increased robustness", "cost benefit and user experi=
ence".  At a minimum, I suggest removing some of this subjectivity and focu=
s on how CDNI will allow for content delivery across multiple CDNs.

In the last paragraph, instead of saying "In order to meet the timelines" -=
- see comment above regarding "short timeframe (18-24 months) as needed by =
the industry."

CDNI Control Interface Requirements:
The following sentence lends to discussing potential solutions.  "We observ=
e that while the CDNI Control interface is currently discussed as a single =
"protocol", further analysis will determine whether the corresponding requi=
rements are to be realized over a single interface and protocol, or over mu=
ltiple interfaces and protocols."  I suggest we remove this from this requi=
rement and make a statement at the beginning along the lines of, "The worki=
ng group attempted to align requirements with the appropriate interface; ho=
wever, solutions to these requirements may apply to a different interface o=
r another interface in addition to the interface it is associated with."

CI-1 =96 Suggest changing this requirement from "=85Downstream CDN (and, if=
 cascaded CDNs are supported by the solution, that the potential cascaded D=
ownstream CDNs) delete=85" to "=85Downstream CDN, including downstream casc=
aded CDNs, delete=85"  Apply this to CI-3, CI-4 and any other similar refer=
ences.  Since, we support cascaded CDNs, then we should simply specify the =
inclusion in the requirement.

CI-4 =96 I think we should require a "reason" to be included with a failure=
 response.  Initially it could simply be a string, unless we are going to s=
imply use HTTP response codes.

CI-8 - "CDNI interconnection" is redundant.  Also, I think "i.e." should be=
 "e.g.".

CDNI Request Routing/Redirection Interface Requirements:
RI-6 appears to be what RI-5 refers to with regards to the "loop prevention=
 mechanism".  If this is the case, I think we should add that language to R=
I-6 and change the order of these two.

CDNI Metadata Distribution Interface Requirements:
MI-16 has a list with only 1 bullet point.  I suggest changing it to, "For =
example, this could potentially including the need to validate URI signed i=
nformation (e.g.  Expiry time, Client IP address)."
MI-21 nit, "Streamin" to "Streaming"; and, this needs to be removed and add=
ressed "[Ed: need to improve wording?]"

CDNI Logging Interface Requirements:
[Same comment as in the CDNI Control Interface Requirements with regards to=
 noting whether it may or may not be multiple protocols.]
LI-13 nit, "requests on via the CDNI" to "requests via the CDNI"

CDNI Security Requirements:
Opening paragraph nit, "Some of those" to "Some of these".

>end.

--_000_CDCA65A1C263dmalascablelabscom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <67B2897F5CC7A24F914914F6E30A2E38@cablelabs.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif; ">
<div>Kent,</div>
<div><br>
</div>
<div>Thanks for your (and Yiu) efforts. &nbsp;Once we have the final revisi=
on, I will start the process of submitting it for AD review. &nbsp;I will b=
e the document shepherd on this draft, also.</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Daryl</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>&quot;Kent Leung (kleung)&quo=
t; &lt;<a href=3D"mailto:kleung@cisco.com">kleung@cisco.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Tuesday, May 28, 2013 12:25 P=
M<br>
<span style=3D"font-weight:bold">To: </span>Daryl Malas &lt;<a href=3D"mail=
to:d.malas@cablelabs.com">d.malas@cablelabs.com</a>&gt;, &quot;<a href=3D"m=
ailto:yiu_lee@cable.comcast.com">yiu_lee@cable.comcast.com</a>&quot; &lt;<a=
 href=3D"mailto:yiu_lee@cable.comcast.com">yiu_lee@cable.comcast.com</a>&gt=
;<br>
<span style=3D"font-weight:bold">Cc: </span>&quot;<a href=3D"mailto:cdni@ie=
tf.org">cdni@ietf.org</a>&quot; &lt;<a href=3D"mailto:cdni@ietf.org">cdni@i=
etf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>RE: [CDNi] Chair review of=
 Requirements draft<br>
</div>
<div><br>
</div>
<div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" x=
mlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:/=
/www.w3.org/TR/REC-html40">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125); ">Hi Daryl. Thanks for your thorough=
 review. We should be able to incorporate your comments into the next versi=
on in a few days.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125); "><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125); ">Kent<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125); "><o:p>&nbsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size: 10pt; font-family: Taho=
ma, sans-serif; ">From:</span></b><span style=3D"font-size: 10pt; font-fami=
ly: Tahoma, sans-serif; "> Daryl Malas [<a href=3D"mailto:D.Malas@cablelabs=
.com">mailto:D.Malas@cablelabs.com</a>]
<br>
<b>Sent:</b> Friday, May 24, 2013 1:35 PM<br>
<b>To:</b> Kent Leung (kleung); <a href=3D"mailto:yiu_lee@cable.comcast.com=
">yiu_lee@cable.comcast.com</a><br>
<b>Cc:</b> <a href=3D"mailto:cdni@ietf.org">cdni@ietf.org</a><br>
<b>Subject:</b> [CDNi] Chair review of Requirements draft<o:p></o:p></span>=
</p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">Kent and Yiu,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; "><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">Here is my chair review of the requirements=
 draft. &nbsp;Overall, I think this draft is in great shape. &nbsp;Let me k=
now if you have any questions.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; "><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">Regards,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; "><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">Daryl<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; "><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">Abstract:<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">I think the cdni WG charter actually descri=
bes the problem better than the text used in the draft. &nbsp;I recommend b=
etter aligning with the charter text - &quot;As
 a result of the significant growth in content delivered over IP&nbsp;netwo=
rks, existing CDN providers are scaling up their infrastructure and&nbsp;ma=
ny Network Service Providers and Enterprise Service Providers are&nbsp;depl=
oying their own CDNs. Subject to the policy of
 the CSP, it is&nbsp;generally desirable that a given item of content can b=
e delivered to an&nbsp;end user regardless of that end user's location or a=
ttachment network. &nbsp;This creates a need for interconnecting (previousl=
y) standalone CDNs so&nbsp;they can interoperate and
 collectively behave as a single delivery&nbsp;infrastructure.&quot;<o:p></=
o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; "><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">Nit - &quot;=85such CDN interconnection.&qu=
ot; to &quot;=85such CDN interconnections.&quot;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; "><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">Remove this sentence - &quot;This draft is =
a work in progress and requirements may be&nbsp;added, modified, or removed=
 by the working group.&quot;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; "><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">The &quot;Requirements Language&quot; shoul=
d be moved to the &quot;Terminology&quot; section.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; "><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">Under the sub-bullets for &quot;high, mediu=
m and low,&quot; I recommend we remove references to compromising the worki=
ng group's schedule. &nbsp;Instead, change these comments
 to indicate the goal in assigning the varying priorities is relative to pr=
oviding a &quot;deployable solution in a short timeframe (18-24 months) as&=
nbsp;needed by the industry.&quot; &nbsp;This is the goal as part of the wo=
rking group charter.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; "><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">Introduction:<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">My experience is that &quot;subjective&quot=
; language should be avoided in IETF drafts. &nbsp;The introduction in this=
 draft is full of subjective phrases: &quot;rapidly increasing
 and expected to continue&quot;, &quot;reduced delivery cost&quot;, &quot;i=
mproved quality of experience&quot;, &quot;increased&nbsp;robustness&quot;,=
 &quot;cost&nbsp;benefit and user experience&quot;. &nbsp;At a minimum, I s=
uggest removing some of this subjectivity and focus on how CDNI will allow =
for content delivery
 across multiple CDNs.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; "><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">In the last paragraph, instead of saying &q=
uot;In order to meet the timelines&quot; -- see comment above regarding &qu=
ot;short timeframe (18-24 months) as needed by the
 industry.&quot;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; "><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">CDNI Control Interface Requirements:<o:p></=
o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">The following sentence lends to discussing =
potential solutions. &nbsp;&quot;We observe that while the CDNI Control int=
erface is&nbsp;currently discussed as a single &quot;protocol&quot;,
 further analysis will&nbsp;determine whether the corresponding requirement=
s are to be realized&nbsp;over a single interface and protocol, or over mul=
tiple interfaces and&nbsp;protocols.&quot; &nbsp;I suggest we remove this f=
rom this requirement and make a statement at the beginning
 along the lines of, &quot;The working group attempted to align requirement=
s with the appropriate interface; however, solutions to these requirements =
may apply to a different interface or another interface in addition to the =
interface it is associated with.&quot;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; "><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">CI-1 =96 Suggest changing this requirement =
from &quot;=85Downstream CDN (and, if cascaded CDNs are&nbsp;supported by t=
he solution, that the potential cascaded&nbsp;Downstream
 CDNs) delete=85&quot; to &quot;=85Downstream CDN, including downstream cas=
caded CDNs, delete=85&quot; &nbsp;Apply this to CI-3, CI-4 and any other si=
milar references. &nbsp;Since, we support cascaded CDNs, then we should sim=
ply specify the inclusion in the requirement.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; "><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">CI-4 =96 I think we should require a &quot;=
reason&quot; to be included with a failure response. &nbsp;Initially it cou=
ld simply be a string, unless we are going to simply
 use HTTP response codes.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; "><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">CI-8 - &quot;CDNI&nbsp;interconnection&quot=
; is redundant. &nbsp;Also, I think &quot;i.e.&quot; should be &quot;e.g.&q=
uot;.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; "><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">CDNI Request Routing/Redirection Interface =
Requirements:<o:p></o:p></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">RI-6 appears to be what RI-5 refers to with=
 regards to the &quot;loop prevention&nbsp;mechanism&quot;. &nbsp;If this i=
s the case, I think we should add that language to RI-6
 and change the order of these two.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; "><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">CDNI Metadata Distribution Interface Requir=
ements:<o:p></o:p></span></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">MI-16 has a list with only 1 bullet point. =
&nbsp;I&nbsp;suggest changing it to, &quot;For example,&nbsp;this could pot=
entially including the&nbsp;need to validate URI signed information
 (e.g. &nbsp;Expiry&nbsp;time, Client IP address).&quot;<o:p></o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">MI-21 nit, &quot;Streamin&quot; to &quot;St=
reaming&quot;; and, this needs to be removed and addressed &quot;[Ed: need&=
nbsp;to improve wording?]&quot;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; "><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">CDNI Logging Interface Requirements:<o:p></=
o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">[Same comment as in the CDNI Control Interf=
ace Requirements with regards to noting whether it may or may not be multip=
le protocols.]<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">LI-13 nit, &quot;requests on via the CDNI&q=
uot; to &quot;requests via the CDNI&quot;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; "><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">CDNI Security Requirements:<o:p></o:p></spa=
n></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">Opening paragraph nit, &quot;Some of those&=
quot; to &quot;Some of these&quot;.<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; "><o:p>&nbsp;</o:p></span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">&gt;end.<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_CDCA65A1C263dmalascablelabscom_--

From kleung@cisco.com  Tue May 28 13:58:50 2013
Return-Path: <kleung@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 7EFA721F8E12 for <cdni@ietfa.amsl.com>; Tue, 28 May 2013 13:58:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 mmY1EG5d33uD for <cdni@ietfa.amsl.com>; Tue, 28 May 2013 13:58:44 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 52AEC21F842A for <cdni@ietf.org>; Tue, 28 May 2013 13:58:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=39030; q=dns/txt; s=iport; t=1369774724; x=1370984324; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=gMi3aNBQfC22DZFiZaSFNpvZioqcOMGO+zfGkeQ/9YE=; b=FaR4ufwOjmHFHRonZl7sYjvUV1r781eqe4bShqx+0bPTnWI4EugeS/hw YmAIpY4L/r6WSvpM/auwTXh1oFWhZQyY/MzQtAf+5U3lQ8Wl21GvIHegM SSiQP7xuqMrLYW6+k5WXc/X/1ZoZzClN6PA6yGywryk/Lmc29l/WsLOXq A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlIGANcZpVGtJXG9/2dsb2JhbABZgkREMMIigQYWdIIjAQEBBC1DBAUQAgEIDgMEAQELFgEGBzIUCQgCBAENBQgTh3K7c41mgQYxBgGCc2EDk2qVEYMPgWkBHgYZ
X-IronPort-AV: E=Sophos;i="4.87,759,1363132800";  d="scan'208,217";a="212944226"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-9.cisco.com with ESMTP; 28 May 2013 20:58:43 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id r4SKwgux011467 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 28 May 2013 20:58:42 GMT
Received: from xmb-aln-x03.cisco.com ([169.254.6.219]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.02.0318.004; Tue, 28 May 2013 15:58:42 -0500
From: "Kent Leung (kleung)" <kleung@cisco.com>
To: Daryl Malas <D.Malas@cablelabs.com>, "yiu_lee@cable.comcast.com" <yiu_lee@cable.comcast.com>
Thread-Topic: [CDNi] Chair review of Requirements draft
Thread-Index: AQHOWL4ol8g/hXc8EEqlADDdC7rE15ka9ZGA
Date: Tue, 28 May 2013 20:58:41 +0000
Message-ID: <CD85F32117029D4F9AEF48BDEF5536AB10265561@xmb-aln-x03.cisco.com>
References: <CDC52B13.C1C6%d.malas@cablelabs.com>
In-Reply-To: <CDC52B13.C1C6%d.malas@cablelabs.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.127.1]
Content-Type: multipart/alternative; boundary="_000_CD85F32117029D4F9AEF48BDEF5536AB10265561xmbalnx03ciscoc_"
MIME-Version: 1.0
Cc: "cdni@ietf.org" <cdni@ietf.org>
Subject: Re: [CDNi] Chair review of Requirements draft
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: Tue, 28 May 2013 20:58:50 -0000

--_000_CD85F32117029D4F9AEF48BDEF5536AB10265561xmbalnx03ciscoc_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Daryl. I'd like to get some clarifications on your points. See below.

From: Daryl Malas [mailto:D.Malas@cablelabs.com]
Sent: Friday, May 24, 2013 1:35 PM
To: Kent Leung (kleung); yiu_lee@cable.comcast.com
Cc: cdni@ietf.org
Subject: [CDNi] Chair review of Requirements draft

Kent and Yiu,

Here is my chair review of the requirements draft.  Overall, I think this d=
raft is in great shape.  Let me know if you have any questions.

Regards,

Daryl

Abstract:
I think the cdni WG charter actually describes the problem better than the =
text used in the draft.  I recommend better aligning with the charter text =
- "As a result of the significant growth in content delivered over IP netwo=
rks, existing CDN providers are scaling up their infrastructure and many Ne=
twork Service Providers and Enterprise Service Providers are deploying thei=
r own CDNs. Subject to the policy of the CSP, it is generally desirable tha=
t a given item of content can be delivered to an end user regardless of tha=
t end user's location or attachment network.  This creates a need for inter=
connecting (previously) standalone CDNs so they can interoperate and collec=
tively behave as a single delivery infrastructure."

Nit - "...such CDN interconnection." to "...such CDN interconnections."

Remove this sentence - "This draft is a work in progress and requirements m=
ay be added, modified, or removed by the working group."

KL> Just want to clarify. Is this text correct for the Abstract section?

"Content Delivery Networks (CDNs) are frequently used for large-scale conte=
nt delivery. As a result of the significant growth in content delivered ove=
r IP networks, existing CDN providers are scaling up their infrastructure a=
nd many Network Service Providers and Enterprise Service Providers are depl=
oying their own CDNs. Subject to the policy of the CSP, it is generally des=
irable that a given item of content can be delivered to an end user regardl=
ess of that end user's location or attachment network.  This creates a need=
 for interconnecting (previously) standalone CDNs so they can interoperate =
and collectively behave as a single delivery infrastructure. The Content Di=
stribution Network Interconnection (CDNI) working group has been chartered =
to develop an interoperable and scalable solution for such CDN interconnect=
ion.

The goal of the present document is to outline the requirements for the sol=
ution and interfaces to be specified by the CDNI working group."

The "Requirements Language" should be moved to the "Terminology" section.

Under the sub-bullets for "high, medium and low," I recommend we remove ref=
erences to compromising the working group's schedule.  Instead, change thes=
e comments to indicate the goal in assigning the varying priorities is rela=
tive to providing a "deployable solution in a short timeframe (18-24 months=
) as needed by the industry."  This is the goal as part of the working grou=
p charter.

KL> Is the following OK?

"   This document uses the terminology defined in section 1.1 of
   Framework for CDNI [I-D.davie-cdni-framework].  In addition, the key
   words "High Priority", "Medium Priority" and "Low Priority" in this
   document are to be interpreted in the following way:

   o  "High Priority" indicates requirements that are to be supported by
      the CDNI interfaces.  A requirement is stated as "High Priority"
      when it is established by the working group that it can be met to
      achieve the goal of a deployable solution in a short timeframe
      (18-24 months) as needed by the industry.  This is tagged as
      "[HIGH]".

   o  "Medium Priority" indicates requirements that are to be supported
      by the CDNI interfaces unless the WG realizes at a later stage
      that attempting to meet this requirement does not achieve the goal
      of a deployable solution in a short timeframe (18-24 months) as
      needed by the industry.  This is tagged as "[MED]".

   o  "Low Priority" indicates requirements that are to be supported by
      the CDNI interfaces provided that dedicating WG resources to this
      work does not prevent addressing "High Priority" and "Medium
      Priority" requirements and that attempting to meet this
      requirement is not an obstacle to achieving the goal of a
      deployable solution in a short timeframe (18-24 months) as needed
      by the industry.  This is tagged as "[LOW]"."

Introduction:
My experience is that "subjective" language should be avoided in IETF draft=
s.  The introduction in this draft is full of subjective phrases: "rapidly =
increasing and expected to continue", "reduced delivery cost", "improved qu=
ality of experience", "increased robustness", "cost benefit and user experi=
ence".  At a minimum, I suggest removing some of this subjectivity and focu=
s on how CDNI will allow for content delivery across multiple CDNs.

In the last paragraph, instead of saying "In order to meet the timelines" -=
- see comment above regarding "short timeframe (18-24 months) as needed by =
the industry."

KL> IMHO, removing the text that describes the rationale for CDN seems to l=
ose the background material that argues for the benefits of interconnecting=
 CDNs. BTW, the rationale is consistent with the CDNI Problem Statement RFC=
.  I think the intended logic is this: Why is a CDN needed now? Why interco=
nnect the CDNs is beneficial? Is the following text OK?

"The volume of video and multimedia content delivered over the Internet is =
rapidly increasing and expected to continue doing so in the future. In the =
face of this growth, Content Delivery Networks (CDNs) provide numerous bene=
fits: reduced delivery cost for cacheable content, improved quality of expe=
rience for end users, and increased robustness of delivery. For these reaso=
ns CDNs are frequently used for large-scale content delivery. As a result o=
f the significant growth in content delivered over IP networks, existing CD=
N providers are scaling up their infrastructure and many Network Service Pr=
oviders and Enterprise Service Providers are deploying their own CDNs. Subj=
ect to the policy of the CSP, it is generally desirable that a given item o=
f content can be delivered to an end user regardless of that end user's loc=
ation or attachment network.  This creates a need for interconnecting (prev=
iously) standalone CDNs so they can interoperate and collectively behave as=
 a single delivery infrastructure. The Content Distribution Network Interco=
nnection (CDNI) working group has been chartered to develop an interoperabl=
e and scalable solution for such CDN interconnections."


CDNI Control Interface Requirements:
The following sentence lends to discussing potential solutions.  "We observ=
e that while the CDNI Control interface is currently discussed as a single =
"protocol", further analysis will determine whether the corresponding requi=
rements are to be realized over a single interface and protocol, or over mu=
ltiple interfaces and protocols."  I suggest we remove this from this requi=
rement and make a statement at the beginning along the lines of, "The worki=
ng group attempted to align requirements with the appropriate interface; ho=
wever, solutions to these requirements may apply to a different interface o=
r another interface in addition to the interface it is associated with."

KL> OK

CI-1 - Suggest changing this requirement from "...Downstream CDN (and, if c=
ascaded CDNs are supported by the solution, that the potential cascaded Dow=
nstream CDNs) delete..." to "...Downstream CDN, including downstream cascad=
ed CDNs, delete..."  Apply this to CI-3, CI-4 and any other similar referen=
ces.  Since, we support cascaded CDNs, then we should simply specify the in=
clusion in the requirement.

CI-4 - I think we should require a "reason" to be included with a failure r=
esponse.  Initially it could simply be a string, unless we are going to sim=
ply use HTTP response codes.

CI-8 - "CDNI interconnection" is redundant.  Also, I think "i.e." should be=
 "e.g.".

KL> OK to CI list.

CDNI Request Routing/Redirection Interface Requirements:
RI-6 appears to be what RI-5 refers to with regards to the "loop prevention=
 mechanism".  If this is the case, I think we should add that language to R=
I-6 and change the order of these two.

KL> RI-6 does not have to be related to loop  prevention. It may be the lev=
el of depth in cascaded CDNs. Limit on the number of redirections may be fo=
r various reasons.

CDNI Metadata Distribution Interface Requirements:
MI-16 has a list with only 1 bullet point.  I suggest changing it to, "For =
example, this could potentially including the need to validate URI signed i=
nformation (e.g.  Expiry time, Client IP address)."
MI-21 nit, "Streamin" to "Streaming"; and, this needs to be removed and add=
ressed "[Ed: need to improve wording?]"

CDNI Logging Interface Requirements:
[Same comment as in the CDNI Control Interface Requirements with regards to=
 noting whether it may or may not be multiple protocols.]
LI-13 nit, "requests on via the CDNI" to "requests via the CDNI"

KL> OK to MI list.

CDNI Security Requirements:
Opening paragraph nit, "Some of those" to "Some of these".

KL> OK.

Kent

>end.

--_000_CD85F32117029D4F9AEF48BDEF5536AB10265561xmbalnx03ciscoc_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi Daryl. I&#8217;d like =
to get some clarifications on your points. See below.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Daryl Ma=
las [mailto:D.Malas@cablelabs.com]
<br>
<b>Sent:</b> Friday, May 24, 2013 1:35 PM<br>
<b>To:</b> Kent Leung (kleung); yiu_lee@cable.comcast.com<br>
<b>Cc:</b> cdni@ietf.org<br>
<b>Subject:</b> [CDNi] Chair review of Requirements draft<o:p></o:p></span>=
</p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">Kent and Yiu,<o:p></o:p></s=
pan></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">Here is my chair review of =
the requirements draft. &nbsp;Overall, I think this draft is in great shape=
. &nbsp;Let me know if you have any questions.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">Regards,<o:p></o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">Daryl<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">Abstract:<o:p></o:p></span>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">I think the cdni WG charter=
 actually describes the problem better than the text used in the draft. &nb=
sp;I recommend better aligning with the charter text - &quot;As a
 result of the significant growth in content delivered over IP&nbsp;network=
s, existing CDN providers are scaling up their infrastructure and&nbsp;many=
 Network Service Providers and Enterprise Service Providers are&nbsp;deploy=
ing their own CDNs. Subject to the policy of the
 CSP, it is&nbsp;generally desirable that a given item of content can be de=
livered to an&nbsp;end user regardless of that end user's location or attac=
hment network. &nbsp;This creates a need for interconnecting (previously) s=
tandalone CDNs so&nbsp;they can interoperate and collectively
 behave as a single delivery&nbsp;infrastructure.&quot;<o:p></o:p></span></=
p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">Nit - &quot;&#8230;such CDN=
 interconnection.&quot; to &quot;&#8230;such CDN interconnections.&quot;<o:=
p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">Remove this sentence - &quo=
t;This draft is a work in progress and requirements may be&nbsp;added, modi=
fied, or removed by the working group.&quot;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">KL&gt; Just want to clari=
fy. Is this text correct for the Abstract section?
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&#8220;Content Delivery N=
etworks (CDNs) are frequently used for large-scale content delivery. As a r=
esult of the significant growth in content delivered over IP networks,
 existing CDN providers are scaling up their infrastructure and many Networ=
k Service Providers and Enterprise Service Providers are deploying their ow=
n CDNs. Subject to the policy of the CSP, it is generally desirable that a =
given item of content can be delivered
 to an end user regardless of that end user's location or attachment networ=
k.&nbsp; This creates a need for interconnecting (previously) standalone CD=
Ns so they can interoperate and collectively behave as a single delivery in=
frastructure. The Content Distribution
 Network Interconnection (CDNI) working group has been chartered to develop=
 an interoperable and scalable solution for such CDN interconnection.<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">The goal of the present d=
ocument is to outline the requirements for the solution and interfaces to b=
e specified by the CDNI working group.&#8221;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">The &quot;Requirements Lang=
uage&quot; should be moved to the &quot;Terminology&quot; section.<o:p></o:=
p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">Under the sub-bullets for &=
quot;high, medium and low,&quot; I recommend we remove references to compro=
mising the working group's schedule. &nbsp;Instead, change these comments
 to indicate the goal in assigning the varying priorities is relative to pr=
oviding a &quot;deployable solution in a short timeframe (18-24 months) as&=
nbsp;needed by the industry.&quot; &nbsp;This is the goal as part of the wo=
rking group charter.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">KL&gt; Is the following O=
K?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&#8220;&nbsp;&nbsp; This =
document uses the terminology defined in section 1.1 of<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp; Framework fo=
r CDNI [I-D.davie-cdni-framework].&nbsp; In addition, the key<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp; words &quot;=
High Priority&quot;, &quot;Medium Priority&quot; and &quot;Low Priority&quo=
t; in this<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp; document are=
 to be interpreted in the following way:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp; o&nbsp; &quo=
t;High Priority&quot; indicates requirements that are to be supported by<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; the CDNI interfaces.&nbsp; A requirement is stated as &quot;High Prio=
rity&quot;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; when it is established by the working group that it can be met to<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; achieve the goal of a deployable solution in a short timeframe<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; (18-24 months) as needed by the industry.&nbsp; This is tagged as<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; &quot;[HIGH]&quot;.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp; o&nbsp; &quo=
t;Medium Priority&quot; indicates requirements that are to be supported<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; by the CDNI interfaces unless the WG realizes at a later stage<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; that attempting to meet this requirement does not achieve the goal<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; of a deployable solution in a short timeframe (18-24 months) as<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; needed by the industry.&nbsp; This is tagged as &quot;[MED]&quot;.<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp; o&nbsp; &quo=
t;Low Priority&quot; indicates requirements that are to be supported by<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; the CDNI interfaces provided that dedicating WG resources to this<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; work does not prevent addressing &quot;High Priority&quot; and &quot;=
Medium<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; Priority&quot; requirements and that attempting to meet this<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; requirement is not an obstacle to achieving the goal of a<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp; &nbsp;=
&nbsp;deployable solution in a short timeframe (18-24 months) as needed<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; by the industry.&nbsp; This is tagged as &quot;[LOW]&quot;.&#8221;<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">Introduction:<o:p></o:p></s=
pan></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">My experience is that &quot=
;subjective&quot; language should be avoided in IETF drafts. &nbsp;The intr=
oduction in this draft is full of subjective phrases: &quot;rapidly increas=
ing
 and expected to continue&quot;, &quot;reduced delivery cost&quot;, &quot;i=
mproved quality of experience&quot;, &quot;increased&nbsp;robustness&quot;,=
 &quot;cost&nbsp;benefit and user experience&quot;. &nbsp;At a minimum, I s=
uggest removing some of this subjectivity and focus on how CDNI will allow =
for content delivery
 across multiple CDNs.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">In the last paragraph, inst=
ead of saying &quot;In order to meet the timelines&quot; -- see comment abo=
ve regarding &quot;short timeframe (18-24 months) as needed by the industry=
.&quot;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">KL&gt; IMHO, removing the=
 text that describes the rationale for CDN seems to lose the background mat=
erial that argues for the benefits of interconnecting CDNs.
 BTW, the rationale is consistent with the CDNI Problem Statement RFC. &nbs=
p;I think the intended logic is this: Why is a CDN needed now? Why intercon=
nect the CDNs is beneficial? Is the following text OK?
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&#8220;The volume of vide=
o and multimedia content delivered over the Internet is rapidly increasing =
and expected to continue doing so in the future. In the face of
 this growth, Content Delivery Networks (CDNs) provide numerous benefits: r=
educed delivery cost for cacheable content, improved quality of experience =
for end users, and increased robustness of delivery. For these reasons CDNs=
 are frequently used for large-scale
 content delivery. As a result of the significant growth in content deliver=
ed over IP networks, existing CDN providers are scaling up their infrastruc=
ture and many Network Service Providers and Enterprise Service Providers ar=
e deploying their own CDNs. Subject
 to the policy of the CSP, it is generally desirable that a given item of c=
ontent can be delivered to an end user regardless of that end user's locati=
on or attachment network.&nbsp; This creates a need for interconnecting (pr=
eviously) standalone CDNs so they can
 interoperate and collectively behave as a single delivery infrastructure. =
The Content Distribution Network Interconnection (CDNI) working group has b=
een chartered to develop an interoperable and scalable solution for such CD=
N interconnections.&#8221;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">CDNI Control Interface Requ=
irements:<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">The following sentence lend=
s to discussing potential solutions. &nbsp;&quot;We observe that while the =
CDNI Control interface is&nbsp;currently discussed as a single &quot;protoc=
ol&quot;,
 further analysis will&nbsp;determine whether the corresponding requirement=
s are to be realized&nbsp;over a single interface and protocol, or over mul=
tiple interfaces and&nbsp;protocols.&quot; &nbsp;I suggest we remove this f=
rom this requirement and make a statement at the beginning
 along the lines of, &quot;The working group attempted to align requirement=
s with the appropriate interface; however, solutions to these requirements =
may apply to a different interface or another interface in addition to the =
interface it is associated with.&quot;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">KL&gt; OK<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">CI-1 &#8211; Suggest changi=
ng this requirement from &quot;&#8230;Downstream CDN (and, if cascaded CDNs=
 are&nbsp;supported by the solution, that the potential cascaded&nbsp;Downs=
tream CDNs)
 delete&#8230;&quot; to &quot;&#8230;Downstream CDN, including downstream c=
ascaded CDNs, delete&#8230;&quot; &nbsp;Apply this to CI-3, CI-4 and any ot=
her similar references. &nbsp;Since, we support cascaded CDNs, then we shou=
ld simply specify the inclusion in the requirement.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">CI-4 &#8211; I think we sho=
uld require a &quot;reason&quot; to be included with a failure response. &n=
bsp;Initially it could simply be a string, unless we are going to simply us=
e
 HTTP response codes.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">CI-8 - &quot;CDNI&nbsp;inte=
rconnection&quot; is redundant. &nbsp;Also, I think &quot;i.e.&quot; should=
 be &quot;e.g.&quot;.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">KL&gt; OK to CI list.<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">CDNI Request Routing/Redire=
ction Interface Requirements:<o:p></o:p></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">RI-6 appears to be what RI-=
5 refers to with regards to the &quot;loop prevention&nbsp;mechanism&quot;.=
 &nbsp;If this is the case, I think we should add that language to RI-6 and
 change the order of these two.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">KL&gt; RI-6 does not have=
 to be related to loop&nbsp; prevention. It may be the level of depth in ca=
scaded CDNs. Limit on the number of redirections may be for various
 reasons.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">CDNI Metadata Distribution =
Interface Requirements:<o:p></o:p></span></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">MI-16 has a list with only =
1 bullet point. &nbsp;I&nbsp;suggest changing it to, &quot;For example,&nbs=
p;this could potentially including the&nbsp;need to validate URI signed inf=
ormation
 (e.g. &nbsp;Expiry&nbsp;time, Client IP address).&quot;<o:p></o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">MI-21 nit, &quot;Streamin&q=
uot; to &quot;Streaming&quot;; and, this needs to be removed and addressed =
&quot;[Ed: need&nbsp;to improve wording?]&quot;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">CDNI Logging Interface Requ=
irements:<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">[Same comment as in the CDN=
I Control Interface Requirements with regards to noting whether it may or m=
ay not be multiple protocols.]<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">LI-13 nit, &quot;requests o=
n via the CDNI&quot; to &quot;requests via the CDNI&quot;<o:p></o:p></span>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">KL&gt; OK to MI list.<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">CDNI Security Requirements:=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">Opening paragraph nit, &quo=
t;Some of those&quot; to &quot;Some of these&quot;.<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">KL&gt; OK.<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Kent<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">&gt;end.<o:p></o:p></span><=
/p>
</div>
</div>
</body>
</html>

--_000_CD85F32117029D4F9AEF48BDEF5536AB10265561xmbalnx03ciscoc_--

From david@mandelberg.org  Tue May 28 16:01:26 2013
Return-Path: <david@mandelberg.org>
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 92DB421F86FB for <cdni@ietfa.amsl.com>; Tue, 28 May 2013 16:01:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.437
X-Spam-Level: 
X-Spam-Status: No, score=-0.437 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  RDNS_NONE=0.1]
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 x7ZXRCbMuOgp for <cdni@ietfa.amsl.com>; Tue, 28 May 2013 16:01:18 -0700 (PDT)
Received: from QMTA11.westchester.pa.mail.comcast.net (qmta11.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:211]) by ietfa.amsl.com (Postfix) with ESMTP id 71B8521F84EF for <cdni@ietf.org>; Tue, 28 May 2013 16:01:17 -0700 (PDT)
Received: from omta16.westchester.pa.mail.comcast.net ([76.96.62.88]) by QMTA11.westchester.pa.mail.comcast.net with comcast id haAV1l0021uE5Es5Bb1HV2; Tue, 28 May 2013 23:01:17 +0000
Received: from uriel.mandelberg.org ([IPv6:2001:4830:11a7:2:216:3eff:fe0e:b38c]) by omta16.westchester.pa.mail.comcast.net with comcast id hb1F1l00F1djk4J3cb1HNV; Tue, 28 May 2013 23:01:17 +0000
Received: from secure.mandelberg.org (unknown [10.1.2.3]) by uriel.mandelberg.org (Postfix) with ESMTP id 3FEC91C6063 for <cdni@ietf.org>; Tue, 28 May 2013 19:07:55 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Date: Tue, 28 May 2013 19:07:55 -0400
From: David Mandelberg <david@mandelberg.org>
To: <cdni@ietf.org>
Message-ID: <096bf0a29c0c3c1c1fdcf955443248f3@mail.mandelberg.org>
X-Sender: david@mandelberg.org
User-Agent: RoundCube Webmail/0.3.1
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1369782077; bh=0osm6UP50PkVGif+4JaxhMgsl0BFwWZseBHewr3jsuA=; h=Received:Received:Received:MIME-Version:Content-Type:Date:From:To: Subject:Message-ID; b=Fa4YNt40cWmYf8PqBgOI9hxlwSSDBEk5KmmniL+LlxI+bG3tRPM3daurMoNEGwb7j 46hr+pmNGilpO7BE++ZhEDUQ2P34/WXLeki/IQaSOzOxNHLlpo778+3wMhjE/niyGk kEnYNAFSE+5t/EzhUUe07qZnf8V8xYhUEJeo3Ma+tDNWCtCdJndPetympA7Jb+rc42 ZkLlsCAEnE+koOXk8dlaCuPQOqwBQBPQ0FCSROCy3hKrDuWNBhYd7PWw3VwZ24+2U7 u5U/SDv6ehQPe4f+3naM6ru8ZzlteIybz63JOyC0QfbqoO633NME4fA5xUtbYtf+Ad SKmnQpvpa2ZnQ==
Subject: [CDNi] logging - hashes
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: Tue, 28 May 2013 23:01:27 -0000

Hi,

I read draft-ietf-cdni-logging-02 and have a few comments about the
Integrity-Hash and Non-Repudiation-Hash directives:

The definition of the Origin directive allows log receivers to modify its
value. However, any modification to the Origin value would invalidate the
Integrity-Hash and Non-Repudiation-Hash.

I don't think the name Non-Repudiation-Hash is accurate. A hash is not
sufficient for non-repudiation, so I think the field should contain a
signature and possibly extra information like the algorithms and public key
used. How about Non-Repudiation-Signature?

The example in section 3.2.2 does not specify the line ending used, so
it's not possible to determine the correct value of Integrity-Hash.

-- 
David Eric Mandelberg / dseomn
http://david.mandelberg.org/

From yiu_lee@cable.comcast.com  Tue May 28 21:20:33 2013
Return-Path: <yiu_lee@cable.comcast.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 A412511E80D2 for <cdni@ietfa.amsl.com>; Tue, 28 May 2013 21:20:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.834
X-Spam-Level: 
X-Spam-Status: No, score=-3.834 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
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 2kLHI8zRX+E3 for <cdni@ietfa.amsl.com>; Tue, 28 May 2013 21:20:27 -0700 (PDT)
Received: from cable.comcast.com (copdcavout01.cable.comcast.com [76.96.32.253]) by ietfa.amsl.com (Postfix) with ESMTP id D1A3521E8053 for <cdni@ietf.org>; Tue, 28 May 2013 21:20:26 -0700 (PDT)
Received: from ([24.40.56.115]) by copdcavout01.cable.comcast.com with ESMTP  id C7WM3M1.73949005; Tue, 28 May 2013 22:18:42 -0600
Received: from PACDCEXHUB05.cable.comcast.com (24.40.56.122) by PACDCEXHUB02.cable.comcast.com (24.40.56.115) with Microsoft SMTP Server (TLS) id 14.2.318.1; Wed, 29 May 2013 00:20:22 -0400
Received: from PACDCEXMB05.cable.comcast.com ([169.254.7.207]) by pacdcexhub05.cable.comcast.com ([fe80::3d40:bdea:7266:7f5a%18]) with mapi id 14.02.0318.001; Wed, 29 May 2013 00:20:22 -0400
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
Thread-Topic: [CDNi] Chair review of Requirements draft
Thread-Index: AQHOXCPVBxPDvS/yrkuQuhid6gUZjA==
Date: Wed, 29 May 2013 04:20:21 +0000
Message-ID: <E3FAB1F4F41F3A45B287E8D9C53522FD472ACB5B@PACDCEXMB05.cable.comcast.com>
In-Reply-To: <CD85F32117029D4F9AEF48BDEF5536AB10265561@xmb-aln-x03.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.4.130416
x-originating-ip: [24.40.55.70]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3452631620_894530"
MIME-Version: 1.0
To: "Kent Leung (kleung)" <kleung@cisco.com>, Daryl Malas <d.malas@cablelabs.com>
X-Mailman-Approved-At: Tue, 28 May 2013 22:34:13 -0700
Cc: "cdni@ietf.org" <cdni@ietf.org>
Subject: Re: [CDNi] Chair review of Requirements draft
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: Wed, 29 May 2013 04:20:33 -0000

--B_3452631620_894530
Content-type: multipart/alternative;
	boundary="B_3452631619_873307"


--B_3452631619_873307
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

Hi Kent and Darly,

I want to make a slight change of the abstract to make it even more
objective:

"Content Delivery Networks (CDNs) are frequently used for content delivery.
As a result of significant growth in content delivered over IP networks,
existing CDN providers are scaling up their infrastructure. Many Network
Service Providers and Enterprise Service Providers are also deploying their
own CDNs. To deliver contents from the Content Service Protect (CSP) to end
users, the contents may traverse across multiple CDNs. This creates a need
for interconnecting (previously) standalone CDNs so that they can
collectively act as a single delivery platform from the CSP to the end
users.

The goal of this memo is to outline the requirements for the CDNI working
group."

What do you guys think?

Thanks,
Yiu

From:  "Kent Leung   (kleung)" <kleung@cisco.com>
Date:  Tuesday, May 28, 2013 4:58 PM
To:  Daryl Malas <D.Malas@cablelabs.com>, "Yiu L. LEE"
<yiu_lee@cable.comcast.com>
Cc:  "cdni@ietf.org" <cdni@ietf.org>
Subject:  RE: [CDNi] Chair review of Requirements draft


KL> Just want to clarify. Is this text correct for the Abstract section?
=20
=B3Content Delivery Networks (CDNs) are frequently used for large-scale
content delivery. As a result of the significant growth in content delivere=
d
over IP networks, existing CDN providers are scaling up their infrastructur=
e
and many Network Service Providers and Enterprise Service Providers are
deploying their own CDNs. Subject to the policy of the CSP, it is generally
desirable that a given item of content can be delivered to an end user
regardless of that end user's location or attachment network.  This creates
a need for interconnecting (previously) standalone CDNs so they can
interoperate and collectively behave as a single delivery infrastructure.
The Content Distribution Network Interconnection (CDNI) working group has
been chartered to develop an interoperable and scalable solution for such
CDN interconnection.
=20
The goal of the present document is to outline the requirements for the
solution and interfaces to be specified by the CDNI working group.=B2



--B_3452631619_873307
Content-type: text/html;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: s=
pace; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size:=
 14px; font-family: Calibri, sans-serif; "><div>Hi Kent and Darly,</div><div=
><br></div><div>I want to make a slight change of the abstract to make it ev=
en more objective:</div><div><br></div><div>"Content Delivery Networks (CDNs=
) are frequently used for content delivery. As a result of significant growt=
h in content delivered over IP networks, existing CDN providers are scaling =
up their infrastructure. Many Network Service Providers and Enterprise Servi=
ce Providers are also deploying their own CDNs. To deliver contents from the=
 Content Service Protect (CSP) to end users, the contents may traverse acros=
s multiple CDNs. This creates a need for interconnecting (previously) standa=
lone CDNs so that they can collectively act as a single delivery platform fr=
om the CSP to the end users.</div><div><br></div><div>The goal of this memo =
is to outline the requirements for the CDNI working group."</div><div><br></=
div><div>What do you guys think?</div><div><br></div><div>Thanks,</div><div>=
Yiu</div><div><br></div><span id=3D"OLK_SRC_BODY_SECTION"><div style=3D"font-fam=
ily:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: me=
dium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in;=
 PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium non=
e; PADDING-TOP: 3pt"><span style=3D"font-weight:bold">From: </span> "Kent Leun=
g   (kleung)" &lt;<a href=3D"mailto:kleung@cisco.com">kleung@cisco.com</a>&gt;=
<br><span style=3D"font-weight:bold">Date: </span> Tuesday, May 28, 2013 4:58 =
PM<br><span style=3D"font-weight:bold">To: </span> Daryl Malas &lt;<a href=3D"ma=
ilto:D.Malas@cablelabs.com">D.Malas@cablelabs.com</a>&gt;, "Yiu L. LEE" &lt;=
<a href=3D"mailto:yiu_lee@cable.comcast.com">yiu_lee@cable.comcast.com</a>&gt;=
<br><span style=3D"font-weight:bold">Cc: </span> "<a href=3D"mailto:cdni@ietf.or=
g">cdni@ietf.org</a>" &lt;<a href=3D"mailto:cdni@ietf.org">cdni@ietf.org</a>&g=
t;<br><span style=3D"font-weight:bold">Subject: </span> RE: [CDNi] Chair revie=
w of Requirements draft<br></div><div><br></div><p class=3D"MsoNormal" style=3D"=
margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', s=
erif; color: rgb(0, 0, 0); font-style: normal; font-variant: normal; font-we=
ight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-=
align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: no=
rmal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-=
text-stroke-width: 0px; "><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125); ">KL&gt; Just want to clarify. Is thi=
s text correct for the Abstract section?<o:p></o:p></span></p><p class=3D"MsoN=
ormal" style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times=
 New Roman', serif; color: rgb(0, 0, 0); font-style: normal; font-variant: n=
ormal; font-weight: normal; letter-spacing: normal; line-height: normal; orp=
hans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; w=
hite-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><span style=3D"font-size: 11pt; font-f=
amily: Calibri, sans-serif; color: rgb(31, 73, 125); "><o:p>&nbsp;</o:p></sp=
an></p><p class=3D"MsoNormal" style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt=
; font-family: 'Times New Roman', serif; color: rgb(0, 0, 0); font-style: no=
rmal; font-variant: normal; font-weight: normal; letter-spacing: normal; lin=
e-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; te=
xt-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webk=
it-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span style=3D"fo=
nt-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">=
&#8220;Content Delivery Networks (CDNs) are frequently used for large-scale =
content delivery. As a result of the significant growth in content delivered=
 over IP networks, existing CDN providers are scaling up their infrastructur=
e and many Network Service Providers and Enterprise Service Providers are de=
ploying their own CDNs. Subject to the policy of the CSP, it is generally de=
sirable that a given item of content can be delivered to an end user regardl=
ess of that end user's location or attachment network.&nbsp; This creates a =
need for interconnecting (previously) standalone CDNs so they can interopera=
te and collectively behave as a single delivery infrastructure. The Content =
Distribution Network Interconnection (CDNI) working group has been chartered=
 to develop an interoperable and scalable solution for such CDN interconnect=
ion.<o:p></o:p></span></p><p class=3D"MsoNormal" style=3D"margin: 0in 0in 0.0001=
pt; font-size: 12pt; font-family: 'Times New Roman', serif; color: rgb(0, 0,=
 0); font-style: normal; font-variant: normal; font-weight: normal; letter-s=
pacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; t=
ext-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-=
spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px=
; "><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: r=
gb(31, 73, 125); "><o:p>&nbsp;</o:p></span></p><p class=3D"MsoNormal" style=3D"m=
argin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', se=
rif; color: rgb(0, 0, 0); font-style: normal; font-variant: normal; font-wei=
ght: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-a=
lign: -webkit-auto; text-indent: 0px; text-transform: none; white-space: nor=
mal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-t=
ext-stroke-width: 0px; "><span style=3D"font-size: 11pt; font-family: Calibri,=
 sans-serif; color: rgb(31, 73, 125); ">The goal of the present document is =
to outline the requirements for the solution and interfaces to be specified =
by the CDNI working group.&#8221;</span></p></span></body></html>

--B_3452631619_873307--

--B_3452631620_894530
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIIVmQYJKoZIhvcNAQcCoIIVijCCFYYCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
EzEwggU0MIIEHKADAgECAhEAzuhISIgzOwSitfbc2LN4WDANBgkqhkiG9w0BAQUFADCBkzEL
MAkGA1UEBhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2Fs
Zm9yZDEaMBgGA1UEChMRQ09NT0RPIENBIExpbWl0ZWQxOTA3BgNVBAMTMENPTU9ETyBDbGll
bnQgQXV0aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTAeFw0xMjA4MjgwMDAwMDBa
Fw0xMzA4MjgyMzU5NTlaMCoxKDAmBgkqhkiG9w0BCQEWGXlpdV9sZWVAY2FibGUuY29tY2Fz
dC5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCscOeu5/EoYRdja1jb6L4x
o0TIevelc17NsPuRHfr2z3BGUMbfsJY1p0uXO9+inBQoBXwb07ac3SbOjA/6Ef3NlMPItWdT
RGeFL6e/sMju9RgVyJURFnFgp7tc2tffnPOupnKZeeRehXeEFjun6+GC6teb1kSMu+WMMaCa
D7/XSK+Q+F0Udc2Av0/gUCkGfTDpNnYwutfctEMRnle6EYUqmJMN4C0crEfovmYdMFFgJLKs
Wa5Cdc+naFoIqzW8AcZB6+1XUDTzFbgjqgUbFFZFPzVZqNxLDFNy4tn8VlRSp2jBhgwQHtk1
ZA+spFENaeUuebp4tczj0IHG683FhhWjAgMBAAGjggHpMIIB5TAfBgNVHSMEGDAWgBR6E04A
dFvGeGNkJ8Ev4qBbvHnFezAdBgNVHQ4EFgQUz03csl7CmjwQY+spX9VWeGb5sVQwDgYDVR0P
AQH/BAQDAgWgMAwGA1UdEwEB/wQCMAAwIAYDVR0lBBkwFwYIKwYBBQUHAwQGCysGAQQBsjEB
AwUCMBEGCWCGSAGG+EIBAQQEAwIFIDBGBgNVHSAEPzA9MDsGDCsGAQQBsjEBAgEBATArMCkG
CCsGAQUFBwIBFh1odHRwczovL3NlY3VyZS5jb21vZG8ubmV0L0NQUzBXBgNVHR8EUDBOMEyg
SqBIhkZodHRwOi8vY3JsLmNvbW9kb2NhLmNvbS9DT01PRE9DbGllbnRBdXRoZW50aWNhdGlv
bmFuZFNlY3VyZUVtYWlsQ0EuY3JsMIGIBggrBgEFBQcBAQR8MHowUgYIKwYBBQUHMAKGRmh0
dHA6Ly9jcnQuY29tb2RvY2EuY29tL0NPTU9ET0NsaWVudEF1dGhlbnRpY2F0aW9uYW5kU2Vj
dXJlRW1haWxDQS5jcnQwJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3NwLmNvbW9kb2NhLmNvbTAk
BgNVHREEHTAbgRl5aXVfbGVlQGNhYmxlLmNvbWNhc3QuY29tMA0GCSqGSIb3DQEBBQUAA4IB
AQBG7LORtWcmzDlw0N/D5AwfsSLe93essAqKFhJ+nt7SmMVBsxGzFnSsZGQHMYQ4UXtiVq9A
NjtPk00F3DC3QGxe4mxdwF9LzeYHpHMpCHTzNyilSimKZolLNBO+MO/U0u79rdF2W+dOAwkB
dzroWBxK+yMhijJn2DCE/1pgxqBz+c9zbAtJYPVpgbeGNvvfIp6CA/JYsupQNqPX49a4MdJ3
L9yXLTiegSE8uPUlCB3sHZclQOXAttuMewpcKDoIC4wZgERKQqRH61PQO100GLKUO+VrTq+f
xNkjOAqA+dih6QO5Djbv3qcMTCcAChJQYK8BS7jved8XgEVa0Ihz7oWKMIIFGjCCBAKgAwIB
AgIQbRnqpxlPajMi5iIyeqpx3jANBgkqhkiG9w0BAQUFADCBrjELMAkGA1UEBhMCVVMxCzAJ
BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJU
UlVTVCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNV
BAMTLVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbDAeFw0x
MTA0MjgwMDAwMDBaFw0yMDA1MzAxMDQ4MzhaMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMS
R3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8g
Q0EgTGltaXRlZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQg
U2VjdXJlIEVtYWlsIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAkoSEW0tX
mNReL4uk4UDIo1NYX2Zl8TJO958yfVXQeExVt0KU4PkncQfFxmmkuTLE8UAakMwnVmJ/F7Vx
aa7lIBvky2NeYMqiQfZq4aP/uN8fSG1lQ4wqLitjOHffsReswtqCAtbUMmrUZ28gE49cNfrl
VICv2HEKHTcKAlBTbJUdqRAUtJmVWRIx/wmi0kzcUtve4kABW0ho3cVKtODtJB86r3FfB+Os
vxQ7sCVxaD30D9YXWEYVgTxoi4uDD216IVfmNLDbMn7jSuGlUnJkJpFOpZIP/+CxYP0ab2hR
mWONGoulzEKbm30iY9OpoPzOnpDfRBn0XFs1uhbzp5v/wQIDAQABo4IBSzCCAUcwHwYDVR0j
BBgwFoAUiYJnfcSdJnAAS7RQSHzePa4Ebn0wHQYDVR0OBBYEFHoTTgB0W8Z4Y2QnwS/ioFu8
ecV7MA4GA1UdDwEB/wQEAwIBBjASBgNVHRMBAf8ECDAGAQH/AgEAMBEGA1UdIAQKMAgwBgYE
VR0gADBYBgNVHR8EUTBPME2gS6BJhkdodHRwOi8vY3JsLnVzZXJ0cnVzdC5jb20vVVROLVVT
RVJGaXJzdC1DbGllbnRBdXRoZW50aWNhdGlvbmFuZEVtYWlsLmNybDB0BggrBgEFBQcBAQRo
MGYwPQYIKwYBBQUHMAKGMWh0dHA6Ly9jcnQudXNlcnRydXN0LmNvbS9VVE5BZGRUcnVzdENs
aWVudF9DQS5jcnQwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVzZXJ0cnVzdC5jb20wDQYJ
KoZIhvcNAQEFBQADggEBAIXWvnhXVW0zf0RS/kLVBqgBA4CK+w2y/Uq/9q9BSfUbWsXSrRtz
bj7pJnzmTJjBMCjfy/tCPKElPgp11tA9OYZm0aGbtU2bb68obB2v5ep0WqjascDxdXovnrqT
ecr+4pEeVnSy+I3T4ENyG+2P/WA5IEf7i686ZUg8mD2lJb+972DgSeUWyOs/Q4Pw4O4NwdPN
M1+b0L1garM7/vrUyTo8H+2b/5tJM75CKTmD7jNpLoKdRU2oadqAGx490hpdfEeZpZsIbRKZ
htZdVwcbpzC+S0lEuJB+ytF5OOu0M/qgOl0mWJ5hVRi0IdWZ1eBDQEIwvuql55TSsP7zdfl/
bucwggSdMIIDhaADAgECAhA0PekrrCc0/4/LNJT7zHBUMA0GCSqGSIb3DQEBBQUAMG8xCzAJ
BgNVBAYTAlNFMRQwEgYDVQQKEwtBZGRUcnVzdCBBQjEmMCQGA1UECxMdQWRkVHJ1c3QgRXh0
ZXJuYWwgVFRQIE5ldHdvcmsxIjAgBgNVBAMTGUFkZFRydXN0IEV4dGVybmFsIENBIFJvb3Qw
HhcNMDUwNjA3MDgwOTEwWhcNMjAwNTMwMTA0ODM4WjCBrjELMAkGA1UEBhMCVVMxCzAJBgNV
BAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT
VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMT
LVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbDCCASIwDQYJ
KoZIhvcNAQEBBQADggEPADCCAQoCggEBALI5haTyfatBO2JGN67NwWB1vDll+UoaR6K5zEjM
apjVTTUZuaRC5c5J4oovHnzSMQfHTrSDZJ0uKdWiZMSFvYVRNXmkTmiQexx6pJKoF/KYFfKT
zMmkMpW7DE8wvZigC4vlbhuiRvp4vKJvq1lepS/Pytptqi/rrKGzaqq3Lmc1i3nhHmmI4uZG
zaCl6r4LznY6eg6b6vzaJ1s9cx8i5khhxkzzabGoLhu21DEgLLyCio6kDqXXiUP8FlqvHXHX
EVnauocNr/rz4cLwpMVnjNbWVDreCqS6A3ezZcj9HtN0YqoYymiTHqGFfvVHZcv4TVcodNI0
/zC27vZiMBSMLOsCAwEAAaOB9DCB8TAfBgNVHSMEGDAWgBStvZh6NLQm9/rEJlTvA73gJMtU
GjAdBgNVHQ4EFgQUiYJnfcSdJnAAS7RQSHzePa4Ebn0wDgYDVR0PAQH/BAQDAgEGMA8GA1Ud
EwEB/wQFMAMBAf8wEQYDVR0gBAowCDAGBgRVHSAAMEQGA1UdHwQ9MDswOaA3oDWGM2h0dHA6
Ly9jcmwudXNlcnRydXN0LmNvbS9BZGRUcnVzdEV4dGVybmFsQ0FSb290LmNybDA1BggrBgEF
BQcBAQQpMCcwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVzZXJ0cnVzdC5jb20wDQYJKoZI
hvcNAQEFBQADggEBAAG8nONjKLDzMQHC33vdYqABnSMxD5ySc1NR6h9M+tafxMovZ354Mw90
FrmRh5H1iib6ZHAA2B75CwRiUIeTgdTa9SPbNLuFVrRwNG54gzcehRzFERWSX4cXvaxq/fHC
0cyJX7F88D5R8jXzfOxgmGs6K+Dv37N9huu1G/Vb7KJ8mBPXAFC50S1z3gN4dOEFhTFey5q5
nZTGuZQ3dXLcRPtn6PD6JR5Sp9ol6UfgoMc8oE6xCjb7d0if75eK+7T+45QUqIO8XC0/0mBx
YO7CcYIM6Yg249ogtKOgbKqWS7iAjnXKSQf2OxS639wF2Z/b4LLmTaB4JufnLW5/X8YeiBUw
ggQ2MIIDHqADAgECAgEBMA0GCSqGSIb3DQEBBQUAMG8xCzAJBgNVBAYTAlNFMRQwEgYDVQQK
EwtBZGRUcnVzdCBBQjEmMCQGA1UECxMdQWRkVHJ1c3QgRXh0ZXJuYWwgVFRQIE5ldHdvcmsx
IjAgBgNVBAMTGUFkZFRydXN0IEV4dGVybmFsIENBIFJvb3QwHhcNMDAwNTMwMTA0ODM4WhcN
MjAwNTMwMTA0ODM4WjBvMQswCQYDVQQGEwJTRTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAk
BgNVBAsTHUFkZFRydXN0IEV4dGVybmFsIFRUUCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVz
dCBFeHRlcm5hbCBDQSBSb290MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAt/ca
M+byAAQtOeBOW+0fvGwPzbX6I7bO3psRM5ekKUx9k5+9SryT7QMa44/P5W1QWtaXKZRagLBJ
etsulf24yr83OC0ePpFBrXBWx/BPP+gynnTKyJBU6cZfD3idmkA8Dqxhql4Uj56HoWpQ3Nea
Tq8Fs6ZxlJxxs1BgCscTnTgHhgKo6ahpJhiQq0ywTyOrOk+E2N/On+Fpb7vXQtdrROTHre5t
QV9yWnEIN7N5ZaRZoJQ39wAvDcKSctrQOHLbFKhFxF0qfbe01sTurM0TRLfJK91DACX6Yblp
algjEbenM49WdVn1zSnXRrcKK2W200JvFbK4e/vv6V1T1TRaJwIDAQABo4HcMIHZMB0GA1Ud
DgQWBBStvZh6NLQm9/rEJlTvA73gJMtUGjALBgNVHQ8EBAMCAQYwDwYDVR0TAQH/BAUwAwEB
/zCBmQYDVR0jBIGRMIGOgBStvZh6NLQm9/rEJlTvA73gJMtUGqFzpHEwbzELMAkGA1UEBhMC
U0UxFDASBgNVBAoTC0FkZFRydXN0IEFCMSYwJAYDVQQLEx1BZGRUcnVzdCBFeHRlcm5hbCBU
VFAgTmV0d29yazEiMCAGA1UEAxMZQWRkVHJ1c3QgRXh0ZXJuYWwgQ0EgUm9vdIIBATANBgkq
hkiG9w0BAQUFAAOCAQEAsJvghSXC1iPiD5YGkp1BmJzZhHmB2R5bFAcjNmWPsNh3u6xBbEdg
g1Gw+TI95/z2JhPHgBalv1r8h894eYkhmuJMBwqGNbzy3lHE0pa33H5O7nD9HDnrDAJRFC2O
vRbgwd9Gdeckrez0QrSFk3AQZ7qdBjVKGNMresxRQqF6Y9Hmu6HFK8I2vhMN5r1jfnl7pwkN
QKtq3Y+Kw/b2jBpCBVHURfWfp2IhaBUgQzyZ53y9JNipkRdziD9WGzE4GLRxD5rNyA6eji4b
4YyYg8sfMfFETMYEc0l2YA/H+L0XgGsu6cxMDlqaeQ8gCi7VnmMmHlWSlNiCF1p70LzHj06G
BDGCAjAwggIsAgEBMIGpMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5j
aGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDE5
MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWls
IENBAhEAzuhISIgzOwSitfbc2LN4WDAJBgUrDgMCGgUAoF0wIwYJKoZIhvcNAQkEMRYEFDlZ
v8se+dS2IpX/Udbw+1jIvYwkMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcN
AQkFMQ8XDTEzMDUyOTA0MjAxOVowDQYJKoZIhvcNAQEBBQAEggEAhN8DFMCH2uVPxz49llWp
GnGfmHURrQErjzRfWSTCFZqfVLqgzAzU2Is4bxBjMGUL5ovzKHfrTBUlHSGcwJp3GT2gZ8+Z
+rIDXKMHAfno23WqAYHNt0z/JhhBeFaHQoY3tfeI93QMTCfs17Ty6PeRYuGP2qQO7XB2U9T9
98y80sHd339HkilNzpVd3T2WcVpu9G6+Jo1tD8rsIMXj6SE1kNUmCxbvu7WDcWIOcXpYNDK1
Xlvn3nKftqthBbg0R5bkcYU6R+vK9JO9OUaiQEam9vRhVz/fmXo+evmwNogR7lG05JTLin2T
kwDV3S7JkjeZZUerGY4sgiGyPGrLS/X3Kw==

--B_3452631620_894530--

From RMurray@velocix.com  Wed May 29 03:17:14 2013
Return-Path: <RMurray@velocix.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 45E9F21F9403 for <cdni@ietfa.amsl.com>; Wed, 29 May 2013 03:17:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 K2X3Q60c2-P9 for <cdni@ietfa.amsl.com>; Wed, 29 May 2013 03:17:08 -0700 (PDT)
Received: from owa.velocix.com (mail-out1.velocix.com [81.134.152.10]) by ietfa.amsl.com (Postfix) with ESMTP id D16F121F9302 for <cdni@ietf.org>; Wed, 29 May 2013 03:16:57 -0700 (PDT)
Received: from EXB01-MLT.corp.velocix.com ([169.254.2.197]) by EXC00CAM.corp.velocix.com ([172.18.4.40]) with mapi id 14.02.0247.003; Wed, 29 May 2013 11:16:55 +0100
From: Rob Murray <RMurray@velocix.com>
To: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
Thread-Topic: CDNI Logging - ucdn-centric-uri
Thread-Index: AQHOW4OGNf9PrN7Okk6NEapp/WOws5kcP6uA
Date: Wed, 29 May 2013 10:16:54 +0000
Message-ID: <49C77373835C5A479BC2A84B2A1D66BD8E461C98@EXB01-MLT.corp.velocix.com>
In-Reply-To: <FC236DA6F2DA77449EF2D02DF4471A8D62FCC1@xmb-rcd-x10.cisco.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.4.130416
x-originating-ip: [135.245.192.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <26763820F3A47849BF4BB656FA9B3ED7@velocix.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "cdni@ietf.org" <cdni@ietf.org>
Subject: Re: [CDNi] CDNI Logging - ucdn-centric-uri
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: Wed, 29 May 2013 10:17:14 -0000

Good idea - that naming makes sense, should avoid a lot of confusion.

-----Original Message-----
From: "Francois Le Faucheur   (flefauch)" <flefauch@cisco.com>
Date: Tuesday, 28 May 2013 14:42
To: Rob Murray <rmurray@velocix.com>
Cc: "cdni@ietf.org" <cdni@ietf.org>
Subject: CDNI Logging - ucdn-centric-uri

>Hi Rob and all,
>
>I've done a little more thinking about your earlier suggestion to
>redefine the ELF "r" prefix into something that designates the uCDN , and
>then rename "ucdn-centric-uri" into "sr-uri".
>
>I'm concluding we should not do that because:
>	* this would probably actually be confusing. When reading "sr-uri" many
>people will probably think this is the uri used by the dCDN surrogate to
>acquire the content from its upstream cache. Case in point, Ben's recent
>message on cs-uri precisely made that exact assumption i.e. "sr-uri would
>be the URI that the surrogate presented to its upstream source on a cache
>miss."=20
>	* if we ever want to define an additional log field related to what
>happens between the surrogate and its upstream cache, the natural "r"
>prefix will be already taken.
>
>So how about we just define new prefixes to refer to uCDN and dCDN when
>needed?
>For example we could coin "u" for uCDN and "d" for dCDN and then we could
>rename "ucdn-centric-uri" into "du-uri"?
>Would that work?
>
>Francois


From iuniana.oprescu@orange.com  Wed May 29 05:21:14 2013
Return-Path: <iuniana.oprescu@orange.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 8A8E321F89E2 for <cdni@ietfa.amsl.com>; Wed, 29 May 2013 05:21:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
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 FbFI4E8fz41y for <cdni@ietfa.amsl.com>; Wed, 29 May 2013 05:21:02 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id AE03121F8976 for <cdni@ietf.org>; Wed, 29 May 2013 05:21:00 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm14.si.francetelecom.fr (ESMTP service) with ESMTP id E4D1022D108; Wed, 29 May 2013 14:20:58 +0200 (CEST)
Received: from PMEXCH21.intranet-paris.francetelecom.fr (unknown [10.100.76.20]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id C6267238055; Wed, 29 May 2013 14:20:58 +0200 (CEST)
Received: from PMEXCB1D.intranet-paris.francetelecom.fr ([10.100.76.13]) by PMEXCH21.intranet-paris.francetelecom.fr ([10.100.76.20]) with mapi; Wed, 29 May 2013 14:20:58 +0200
From: <iuniana.oprescu@orange.com>
To: Rob Murray <RMurray@velocix.com>, "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
Date: Wed, 29 May 2013 14:20:57 +0200
Thread-Topic: CDNI Logging - ucdn-centric-uri
Thread-Index: AQHOW4OGNf9PrN7Okk6NEapp/WOws5kcP6uA///SZgA=
Message-ID: <28483_1369830058_51A5F2AA_28483_1917_1_8F0D2F5E4AAB7249BC7339A3E944DEDD20EC448892@PMEXCB1D.intranet-paris.francetelecom.fr>
References: <FC236DA6F2DA77449EF2D02DF4471A8D62FCC1@xmb-rcd-x10.cisco.com> <49C77373835C5A479BC2A84B2A1D66BD8E461C98@EXB01-MLT.corp.velocix.com>
In-Reply-To: <49C77373835C5A479BC2A84B2A1D66BD8E461C98@EXB01-MLT.corp.velocix.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.5.21.113319
Cc: "cdni@ietf.org" <cdni@ietf.org>
Subject: Re: [CDNi] CDNI Logging - ucdn-centric-uri
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: Wed, 29 May 2013 12:21:14 -0000

Yes, I think too this is a good idea beacuse the r and s meanings were not =
that clear, depending on the context. We can discuss this in more detail th=
is afternoon.

Cheers,
-- iuniana=20=20

-----Message d'origine-----
De : cdni-bounces@ietf.org [mailto:cdni-bounces@ietf.org] De la part de Rob=
 Murray
Envoy=E9 : mercredi 29 mai 2013 12:17
=C0 : Francois Le Faucheur (flefauch)
Cc : cdni@ietf.org
Objet : Re: [CDNi] CDNI Logging - ucdn-centric-uri

Good idea - that naming makes sense, should avoid a lot of confusion.

-----Original Message-----
From: "Francois Le Faucheur   (flefauch)" <flefauch@cisco.com>
Date: Tuesday, 28 May 2013 14:42
To: Rob Murray <rmurray@velocix.com>
Cc: "cdni@ietf.org" <cdni@ietf.org>
Subject: CDNI Logging - ucdn-centric-uri

>Hi Rob and all,
>
>I've done a little more thinking about your earlier suggestion to=20
>redefine the ELF "r" prefix into something that designates the uCDN ,=20
>and then rename "ucdn-centric-uri" into "sr-uri".
>
>I'm concluding we should not do that because:
>	* this would probably actually be confusing. When reading "sr-uri"=20
>many people will probably think this is the uri used by the dCDN=20
>surrogate to acquire the content from its upstream cache. Case in=20
>point, Ben's recent message on cs-uri precisely made that exact=20
>assumption i.e. "sr-uri would be the URI that the surrogate presented=20
>to its upstream source on a cache miss."
>	* if we ever want to define an additional log field related to what=20
>happens between the surrogate and its upstream cache, the natural "r"
>prefix will be already taken.
>
>So how about we just define new prefixes to refer to uCDN and dCDN when=20
>needed?
>For example we could coin "u" for uCDN and "d" for dCDN and then we=20
>could rename "ucdn-centric-uri" into "du-uri"?
>Would that work?
>
>Francois

_______________________________________________
CDNi mailing list
CDNi@ietf.org
https://www.ietf.org/mailman/listinfo/cdni

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for message=
s that have been modified, changed or falsified.
Thank you.


From flefauch@cisco.com  Wed May 29 07:31:58 2013
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 B58C921F84B5 for <cdni@ietfa.amsl.com>; Wed, 29 May 2013 07:31:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 QS9D+iv-+PnV for <cdni@ietfa.amsl.com>; Wed, 29 May 2013 07:31:54 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id CDDD321F86CA for <cdni@ietf.org>; Wed, 29 May 2013 07:31:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3805; q=dns/txt; s=iport; t=1369837914; x=1371047514; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=I9oxQvXZyTYev6gsqktBfZD12PFr8BpFBUgFs1/9w3k=; b=l0npJYt0hNfNNqmm6T7oChvkAcTUuBVmi73hamIvZNqjyKjiTj+FFayf 3m/OCWydscglKbd3+WKo6x5/CrI65jKa3QU28reneooP4bLTjUyDc9VeD n0UL+ylac/95KowuRXAgouZMVU+TeiK1DdIr6dfom0bMF8JIxc+u+dSPN c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlwIAMsQplGtJV2b/2dsb2JhbABagwkwwX2BCRZtB4IjAQEBAwEBAQFrCwUHBAIBCBEDAQILHQcnCxQJCAIEDgUIh38GDLo9BI1RgQ8CMQcGgnBhA4hnoBSDD4FxNg
X-IronPort-AV: E=Sophos;i="4.87,764,1363132800"; d="scan'208";a="216250139"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-7.cisco.com with ESMTP; 29 May 2013 14:31:51 +0000
Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r4TEVpqB017443 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 29 May 2013 14:31:51 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.56]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.02.0318.004; Wed, 29 May 2013 09:31:51 -0500
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "iuniana.oprescu@orange.com" <iuniana.oprescu@orange.com>
Thread-Topic: CDNI Logging - ucdn-centric-uri
Thread-Index: AQHOW4OGNf9PrN7Okk6NEapp/WOws5kcP6uA///SZgCAAH07gA==
Date: Wed, 29 May 2013 14:31:50 +0000
Message-ID: <FC236DA6F2DA77449EF2D02DF4471A8D633AD6@xmb-rcd-x10.cisco.com>
References: <FC236DA6F2DA77449EF2D02DF4471A8D62FCC1@xmb-rcd-x10.cisco.com> <49C77373835C5A479BC2A84B2A1D66BD8E461C98@EXB01-MLT.corp.velocix.com> <28483_1369830058_51A5F2AA_28483_1917_1_8F0D2F5E4AAB7249BC7339A3E944DEDD20EC448892@PMEXCB1D.intranet-paris.francetelecom.fr>
In-Reply-To: <28483_1369830058_51A5F2AA_28483_1917_1_8F0D2F5E4AAB7249BC7339A3E944DEDD20EC448892@PMEXCB1D.intranet-paris.francetelecom.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.55.161.201]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <18165AA047DEB048B9963B579CD0B084@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "cdni@ietf.org" <cdni@ietf.org>
Subject: Re: [CDNi] CDNI Logging - ucdn-centric-uri
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: Wed, 29 May 2013 14:31:58 -0000

So I think we have agreement to go ahead with "u" and "d" prefixes. Good.

Now, with respect to renaming the "ucdn-centric-uri", I think we may want t=
o call this field "u-uri" (instead of my earlier proposal of "du-uri") beca=
use this uri is intended to be meaningful to the uCDN but it may or may not=
 exactly coincide with the uri that is used for actual content acquisition =
by dCDN from uCDN (which would be the "du-uri").

Bottom line, I propose we rename "ucdn-centric-uri" into "u-uri".


On 29 May 2013, at 14:20, iuniana.oprescu@orange.com wrote:

> Yes, I think too this is a good idea beacuse the r and s meanings were no=
t that clear, depending on the context. We can discuss this in more detail =
this afternoon.
>=20
> Cheers,
> -- iuniana =20
>=20
> -----Message d'origine-----
> De : cdni-bounces@ietf.org [mailto:cdni-bounces@ietf.org] De la part de R=
ob Murray
> Envoy=E9 : mercredi 29 mai 2013 12:17
> =C0 : Francois Le Faucheur (flefauch)
> Cc : cdni@ietf.org
> Objet : Re: [CDNi] CDNI Logging - ucdn-centric-uri
>=20
> Good idea - that naming makes sense, should avoid a lot of confusion.
>=20
> -----Original Message-----
> From: "Francois Le Faucheur   (flefauch)" <flefauch@cisco.com>
> Date: Tuesday, 28 May 2013 14:42
> To: Rob Murray <rmurray@velocix.com>
> Cc: "cdni@ietf.org" <cdni@ietf.org>
> Subject: CDNI Logging - ucdn-centric-uri
>=20
>> Hi Rob and all,
>>=20
>> I've done a little more thinking about your earlier suggestion to=20
>> redefine the ELF "r" prefix into something that designates the uCDN ,=20
>> and then rename "ucdn-centric-uri" into "sr-uri".
>>=20
>> I'm concluding we should not do that because:
>> 	* this would probably actually be confusing. When reading "sr-uri"=20
>> many people will probably think this is the uri used by the dCDN=20
>> surrogate to acquire the content from its upstream cache. Case in=20
>> point, Ben's recent message on cs-uri precisely made that exact=20
>> assumption i.e. "sr-uri would be the URI that the surrogate presented=20
>> to its upstream source on a cache miss."
>> 	* if we ever want to define an additional log field related to what=20
>> happens between the surrogate and its upstream cache, the natural "r"
>> prefix will be already taken.
>>=20
>> So how about we just define new prefixes to refer to uCDN and dCDN when=
=20
>> needed?
>> For example we could coin "u" for uCDN and "d" for dCDN and then we=20
>> could rename "ucdn-centric-uri" into "du-uri"?
>> Would that work?
>>=20
>> Francois
>=20
> _______________________________________________
> CDNi mailing list
> CDNi@ietf.org
> https://www.ietf.org/mailman/listinfo/cdni
>=20
> _________________________________________________________________________=
________________________________________________
>=20
> Ce message et ses pieces jointes peuvent contenir des informations confid=
entielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez re=
cu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages =
electroniques etant susceptibles d'alteration,
> France Telecom - Orange decline toute responsabilite si ce message a ete =
altere, deforme ou falsifie. Merci.
>=20
> This message and its attachments may contain confidential or privileged i=
nformation that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and de=
lete this message and its attachments.
> As emails may be altered, France Telecom - Orange is not liable for messa=
ges that have been modified, changed or falsified.
> Thank you.
>=20


From flefauch@cisco.com  Wed May 29 07:47:53 2013
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 221F421F90EE for <cdni@ietfa.amsl.com>; Wed, 29 May 2013 07:47:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.298
X-Spam-Level: 
X-Spam-Status: No, score=-10.298 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_63=0.6, 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 4Jg+8Qq+Sn2G for <cdni@ietfa.amsl.com>; Wed, 29 May 2013 07:47:48 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id BD29A21F8899 for <cdni@ietf.org>; Wed, 29 May 2013 07:47:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4842; q=dns/txt; s=iport; t=1369838867; x=1371048467; h=from:to:subject:date:message-id:references:mime-version; bh=DOV9ifanx2+urGrxKkp0LU6QPw5RspyBnZj0VLidf8Q=; b=SvYZImM15a8xaohegVvzcGwsD6k1sXtjQ00I80CjBX3Ro/kosykEowLn piN97SrJaBX3MHLyEq5hykCWNC9i4hvHV1OQZE4m789yfeeQuwAMP39dN GK3+6a5+AjoiRvCqoxJuxz4+5mWxjQEPJHbftI31SeAhdymCa8KZbx8YB E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Al0IAEUUplGtJXHA/2dsb2JhbABAFwOCRUQwwX2BChZtB4IkAQECAmYCIQIBDBAOCgQMCjIkAQIBAxuIBQwyrCuNao1RG3YgAQwcB4JeYQOoe4I/UIFxNg
X-IronPort-AV: E=Sophos;i="4.87,764,1363132800";  d="scan'208,217";a="216067195"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-1.cisco.com with ESMTP; 29 May 2013 14:47:41 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r4TElefH023386 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <cdni@ietf.org>; Wed, 29 May 2013 14:47:40 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.56]) by xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.02.0318.004; Wed, 29 May 2013 09:47:40 -0500
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "cdni@ietf.org" <cdni@ietf.org>
Thread-Topic: CDNI Logging -Informal Meeting starts in 15 mins
Thread-Index: AQHOXHt3PyGzKA/L/UuMfrl58KdW8g==
Date: Wed, 29 May 2013 14:47:40 +0000
Message-ID: <FC236DA6F2DA77449EF2D02DF4471A8D633CDD@xmb-rcd-x10.cisco.com>
References: <FC236DA6F2DA77449EF2D02DF4471A8D62E927@xmb-rcd-x10.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.55.161.201]
Content-Type: multipart/alternative; boundary="_000_FC236DA6F2DA77449EF2D02DF4471A8D633CDDxmbrcdx10ciscocom_"
MIME-Version: 1.0
Subject: [CDNi] CDNI Logging -Informal Meeting starts in 15 mins
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: Wed, 29 May 2013 14:47:53 -0000

--_000_FC236DA6F2DA77449EF2D02DF4471A8D633CDDxmbrcdx10ciscocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Topic: IETF CDNI Logging - Informal Meeting
Date: Wednesday, May 29, 2013
Time: 5:00 pm, Europe Summer Time (Paris, GMT+02:00)
Meeting Number: 205 636 967
Password: cdni

-------------------------------------------------------
To join the meeting online(Now from mobile devices!)
-------------------------------------------------------
1. Go to https://cisco.webex.com/ciscosales/j.php?ED=3D225213752&UID=3D4843=
18167&PW=3DNNTMwZTVjNGRk&RT=3DMiMyMw%3D%3D
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: cdni
4. Click "Join".
5. If the meeting includes a teleconference, follow the instructions that a=
ppear on your screen.

-------------------------------------------------------
To join the audio conference only
-------------------------------------------------------
To receive a call back, provide your phone number when you join the meeting=
, or call the number below and enter the access code.
Call-in toll-free number (US/Canada): +1-866-432-9903
Call-in toll number (US/Canada): +1-408-525-6800
Toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restricti=
ons.pdf

Access code:205 636 967

CCP:+14085256800x205636967#





--_000_FC236DA6F2DA77449EF2D02DF4471A8D633CDDxmbrcdx10ciscocom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <DAB242A9F0266340BB90D307BBAB80E6@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<blockquote type=3D"cite">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; ">
<blockquote type=3D"cite">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; ">
<blockquote type=3D"cite">
<div lang=3D"FR" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1" style=3D"page: WordSection1; ">
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif; ">
<span style=3D"font-family: Tahoma, sans-serif; ">Topic: IETF CDNI Logging =
- Informal Meeting&nbsp;<br>
<b><span style=3D"color: rgb(145, 38, 4); ">Date: Wednesday, May 29, 2013&n=
bsp;</span></b><br>
Time: 5:00 pm, Europe Summer Time (Paris, GMT&#43;02:00)&nbsp;<br>
Meeting Number: 205 636 967&nbsp;<br>
Password: cdni&nbsp;<br>
<br>
-------------------------------------------------------&nbsp;<br>
To join the meeting online(Now from mobile devices!)&nbsp;<br>
-------------------------------------------------------&nbsp;<br>
1. Go to&nbsp;</span><a href=3D"https://cisco.webex.com/ciscosales/j.php?ED=
=3D225213752&amp;UID=3D484318167&amp;PW=3DNNTMwZTVjNGRk&amp;RT=3DMiMyMw%3D%=
3D" target=3D"_blank" style=3D"color: purple; "><span style=3D"font-family:=
 Tahoma, sans-serif; ">https://cisco.webex.com/ciscosales/j.php?ED=3D225213=
752&amp;UID=3D484318167&amp;PW=3DNNTMwZTVjNGRk&amp;RT=3DMiMyMw%3D%3D</span>=
</a><span style=3D"font-family: Tahoma, sans-serif; ">&nbsp;<br>
2. If requested, enter your name and email address.&nbsp;<br>
3. If a password is required, enter the meeting password: cdni&nbsp;<br>
4. Click &quot;Join&quot;.&nbsp;<br>
5. If the meeting includes a teleconference, follow the instructions that a=
ppear on your screen.&nbsp;<br>
<br>
-------------------------------------------------------&nbsp;<br>
To join the audio conference only&nbsp;<br>
-------------------------------------------------------&nbsp;<br>
To receive a call back, provide your phone number when you join the meeting=
, or call the number below and enter the access code.&nbsp;<br>
Call-in toll-free number (US/Canada): &#43;1-866-432-9903&nbsp;<br>
Call-in toll number (US/Canada): &#43;1-408-525-6800&nbsp;<br>
Toll-free dialing restrictions:&nbsp;</span><a href=3D"http://www.webex.com=
/pdf/tollfree_restrictions.pdf" target=3D"_blank" style=3D"color: purple; "=
><span style=3D"font-family: Tahoma, sans-serif; ">http://www.webex.com/pdf=
/tollfree_restrictions.pdf</span></a><span style=3D"font-family: Tahoma, sa=
ns-serif; ">&nbsp;<br>
<br>
Access code:205 636 967&nbsp;<br>
<br>
CCP:&#43;14085256800x205636967#&nbsp;<br>
</span></div>
</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</div>
<div><br>
</div>
<div><br>
</div>
<div>
<blockquote type=3D"cite"><br>
</blockquote>
</div>
<br>
</body>
</html>

--_000_FC236DA6F2DA77449EF2D02DF4471A8D633CDDxmbrcdx10ciscocom_--

From flefauch@cisco.com  Wed May 29 07:49:44 2013
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 4172421F911B for <cdni@ietfa.amsl.com>; Wed, 29 May 2013 07:49:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.556
X-Spam-Level: 
X-Spam-Status: No, score=-10.556 tagged_above=-999 required=5 tests=[AWL=0.043, 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 QsngF9AAcyqx for <cdni@ietfa.amsl.com>; Wed, 29 May 2013 07:49:39 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 98C4921F9113 for <cdni@ietf.org>; Wed, 29 May 2013 07:49:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2061; q=dns/txt; s=iport; t=1369838978; x=1371048578; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=teZNSfOfoeg43f9pyeymhnljrHzujcNN4MDbQieXynY=; b=BjuDRodptxGAqNkA758RAKxfTM9XEIZaAWbgJItTjnrxaPu5ulp6xkc7 hMXbJw1pQfT0a1einVIXbt9wIXmCxvmN5lw9chwJmgCXX1gmWReMCSkyZ hRKSC73Go2YGhI5CTR4a6TvPVtV/53RRpLq+KojGp0KyYBk1XVzAlZvBM U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AosGAEUUplGtJV2Y/2dsb2JhbABagwkwwX2BChZ0giMBAQEDAQEBATc0CwULAgEIIhQQJwslAgQOBQiHfwYMukeOYAIxB4J2YQOYZJAXgw+CJw
X-IronPort-AV: E=Sophos;i="4.87,764,1363132800"; d="scan'208";a="216068053"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-1.cisco.com with ESMTP; 29 May 2013 14:49:37 +0000
Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r4TEnZ93011625 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 29 May 2013 14:49:35 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.56]) by xhc-rcd-x01.cisco.com ([173.37.183.75]) with mapi id 14.02.0318.004; Wed, 29 May 2013 09:49:35 -0500
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: David Mandelberg <david@mandelberg.org>
Thread-Topic: [CDNi] logging - hashes
Thread-Index: AQHOW/dLtTMxXqYq5kSdi64whUD/l5kck1oA
Date: Wed, 29 May 2013 14:49:34 +0000
Message-ID: <FC236DA6F2DA77449EF2D02DF4471A8D633D45@xmb-rcd-x10.cisco.com>
References: <096bf0a29c0c3c1c1fdcf955443248f3@mail.mandelberg.org>
In-Reply-To: <096bf0a29c0c3c1c1fdcf955443248f3@mail.mandelberg.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.55.161.201]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <7461235876EB634B9C3ACCC0C172FA12@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<cdni@ietf.org>" <cdni@ietf.org>
Subject: Re: [CDNi] logging - hashes
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: Wed, 29 May 2013 14:49:44 -0000

On 29 May 2013, at 01:07, David Mandelberg <david@mandelberg.org> wrote:

> Hi,
>=20
> I read draft-ietf-cdni-logging-02 and have a few comments about the
> Integrity-Hash and Non-Repudiation-Hash directives:
>=20
> The definition of the Origin directive allows log receivers to modify its
> value. However, any modification to the Origin value would invalidate the
> Integrity-Hash and Non-Repudiation-Hash.

Good point.
There are several ways to go about that.=20

For Integrity-hash, it does not involve any "secret" and is computationally=
 light. So we could just specify that it needs to be recomputed when Origin=
 is modified. (We could also specify that the Integrity-Hash excludes the O=
rigin directive, but that seems undesirable to not cover that field which i=
s quite significant).

For Non-Repudiation-Hash/Signature, I believe, by definition it cannot be r=
ecomputed by the uCDN. But arguably, if there is a Non-Repudiation-Hash/Sig=
nature then, the Origin could be trusted (at leafs as much as the rest of t=
he logging file). So we could mandate that when Non-Repudiation-Hash/Signat=
ure directive is included, then the Origin must be provided by dCDN and mus=
t not be modified by uCDN.

Thoughts?

>=20
> I don't think the name Non-Repudiation-Hash is accurate. A hash is not
> sufficient for non-repudiation, so I think the field should contain a
> signature and possibly extra information like the algorithms and public k=
ey
> used.

Let's discuss during the Informal Meeting (I hope you can attend).

> How about Non-Repudiation-Signature?

Works for me.

>=20
> The example in section 3.2.2 does not specify the line ending used, =20

as in whether it is LF or CRLF?

Thanks

Francois

> so
> it's not possible to determine the correct value of Integrity-Hash.
>=20
> --=20
> David Eric Mandelberg / dseomn
> http://david.mandelberg.org/
> _______________________________________________
> CDNi mailing list
> CDNi@ietf.org
> https://www.ietf.org/mailman/listinfo/cdni


From david@mandelberg.org  Wed May 29 09:43:41 2013
Return-Path: <david@mandelberg.org>
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 0512121F96D0 for <cdni@ietfa.amsl.com>; Wed, 29 May 2013 09:43:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.437
X-Spam-Level: 
X-Spam-Status: No, score=-0.437 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  RDNS_NONE=0.1]
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 6X07A9lRlVMi for <cdni@ietfa.amsl.com>; Wed, 29 May 2013 09:43:31 -0700 (PDT)
Received: from qmta15.westchester.pa.mail.comcast.net (qmta15.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:228]) by ietfa.amsl.com (Postfix) with ESMTP id AECEF21F96CB for <cdni@ietf.org>; Wed, 29 May 2013 09:43:31 -0700 (PDT)
Received: from omta15.westchester.pa.mail.comcast.net ([76.96.62.87]) by qmta15.westchester.pa.mail.comcast.net with comcast id hnPq1l0071swQuc5FsjXu9; Wed, 29 May 2013 16:43:31 +0000
Received: from uriel.mandelberg.org ([IPv6:2001:4830:11a7:2:216:3eff:fe0e:b38c]) by omta15.westchester.pa.mail.comcast.net with comcast id hsjU1l00W1djk4J3bsjWq7; Wed, 29 May 2013 16:43:31 +0000
Received: from secure.mandelberg.org (unknown [10.1.2.3]) by uriel.mandelberg.org (Postfix) with ESMTP id 144421C6063; Wed, 29 May 2013 12:50:15 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Date: Wed, 29 May 2013 12:50:15 -0400
From: David Mandelberg <david@mandelberg.org>
To: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
In-Reply-To: <FC236DA6F2DA77449EF2D02DF4471A8D633D45@xmb-rcd-x10.cisco.com>
References: <096bf0a29c0c3c1c1fdcf955443248f3@mail.mandelberg.org> <FC236DA6F2DA77449EF2D02DF4471A8D633D45@xmb-rcd-x10.cisco.com>
Message-ID: <88e2ddc21a450716032bf1273cae1ec3@mail.mandelberg.org>
X-Sender: david@mandelberg.org
User-Agent: RoundCube Webmail/0.3.1
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1369845811; bh=PEVlW1cKHrqESmIQEQQyF5a57cHCoS3XqBjGDfDOn20=; h=Received:Received:Received:MIME-Version:Content-Type:Date:From:To: Subject:Message-ID; b=k/9MzA8I6wsZPfBJInGyIinp32BlOLKCTSRuWC69JJb41iWc0s9Xbjq7ZUr3SgjiQ xRyclAne6eBy4HPI60U5xDD5KgPdFpvxgRn7PPqDaoujIJL7iSvHttUIDavRlmmwKZ Rg6r/AzygJHAn4f3/iCcw6ASI4vYYC+Oe2h5OGeZ9TLZg/7pFrSdT9rJi7W7ePlcow oMdTPNDYkaF6dKk+IuqDx3/hvixgqlekToJt5l6+bLrgQy/lK6WfJu8CmwTqy+dvrL MGvOKSN8lz8finDmLS5OQC/+CzJ0lupj+0V1LCsgRi6gabxrKzMQqdlekWnIiGpTeL 3DICaYeMloFXg==
Cc: <cdni@ietf.org>
Subject: Re: [CDNi] logging - hashes
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: Wed, 29 May 2013 16:43:41 -0000

On Wed, 29 May 2013 14:49:34 +0000, "Francois Le Faucheur (flefauch)"
<flefauch@cisco.com> wrote:
> On 29 May 2013, at 01:07, David Mandelberg <david@mandelberg.org> wrote:
>> The example in section 3.2.2 does not specify the line ending used,  
> 
> as in whether it is LF or CRLF?

Yes.

[Not responding to the other parts of your email because we discussed them
in the informal meeting.]

-- 
David Eric Mandelberg / dseomn
http://david.mandelberg.org/

From david@mandelberg.org  Thu May 30 10:21:32 2013
Return-Path: <david@mandelberg.org>
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 D2C8F21F8619 for <cdni@ietfa.amsl.com>; Thu, 30 May 2013 10:21:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.437
X-Spam-Level: 
X-Spam-Status: No, score=-0.437 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  RDNS_NONE=0.1]
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 PrKGxfbTMKQ6 for <cdni@ietfa.amsl.com>; Thu, 30 May 2013 10:21:28 -0700 (PDT)
Received: from qmta12.emeryville.ca.mail.comcast.net (qmta12.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:44:76:96:27:227]) by ietfa.amsl.com (Postfix) with ESMTP id 9D3D121F960C for <cdni@ietf.org>; Thu, 30 May 2013 10:21:25 -0700 (PDT)
Received: from omta06.emeryville.ca.mail.comcast.net ([76.96.30.51]) by qmta12.emeryville.ca.mail.comcast.net with comcast id iF8d1l00516AWCU01HMRVL; Thu, 30 May 2013 17:21:25 +0000
Received: from uriel.mandelberg.org ([IPv6:2001:4830:11a7:2:216:3eff:fe0e:b38c]) by omta06.emeryville.ca.mail.comcast.net with comcast id iHMN1l00i1djk4J8SHMQ8a; Thu, 30 May 2013 17:21:25 +0000
Received: from secure.mandelberg.org (unknown [10.1.2.3]) by uriel.mandelberg.org (Postfix) with ESMTP id 3B0ED1C6063 for <cdni@ietf.org>; Thu, 30 May 2013 13:28:18 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Date: Thu, 30 May 2013 13:28:18 -0400
From: David Mandelberg <david@mandelberg.org>
To: <cdni@ietf.org>
Message-ID: <203799ab055aceac432998afe6bca638@mail.mandelberg.org>
X-Sender: david@mandelberg.org
User-Agent: RoundCube Webmail/0.3.1
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1369934485; bh=Eu0WupwqolH9AHW9snEAJYTkIjt80rXHUrJ5Frm7/to=; h=Received:Received:Received:MIME-Version:Content-Type:Date:From:To: Subject:Message-ID; b=Jc3//oHYngB6/yUx8I+7Tyr3zNCCcu7oS3BcThhzrHWzlWbDtyH6sppR3PI1mqhiW /iegGlM+dykcaehT0483sZOwTv29CBOgfUerqtS/UxxW7mUq9wWHkroepYIs09dlXf iUmGD4X+f929gmKqj5EIOEljig6+1MJ2pJJAt5x8ErGfdkQCCKBl/wLFakAbqiXdpo XYpVtwcrg82x3KO0bYDJnD1Luj21GXV7TTGjL399p1rz8e7Ixsm8if1YqIko9YBxLJ ahxChObXMI9B7XIn3w72xPCcHBO/45gncZkoPhiXLnRQBYWQL9oTv2FC2ayvq67nzT uYA5kssryDW6w==
Subject: [CDNi] non-repudiation questions
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: Thu, 30 May 2013 17:21:33 -0000

Hi,

What are the goals of non-repudiation of logging data? I've listed two
possibilities below. Are those right? Is there anything else that people
want non-repudiation to do for them?

 * Audits: If a uCDN detects a problem that's supported by logging
information, the dCDN can't claim that they never supplied that logging
information or that the information was modified in transit.
 * Billing: Once a uCDN receives a log file, the dCDN can't claim that
there are additional records that are missing from that file. (But they can
still add those records to a future log file.)

Also, how would dCDNs be willing to protect their private keys? If dCDNs
don't want to use hardware security modules, I'd recommend a solution that
uses ephemeral keys.

-- 
David Eric Mandelberg / dseomn
http://david.mandelberg.org/

From iuniana.oprescu@orange.com  Thu May 30 10:24:21 2013
Return-Path: <iuniana.oprescu@orange.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 48C0D21F9354 for <cdni@ietfa.amsl.com>; Thu, 30 May 2013 10:24:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
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 KpLGKiPr6Zje for <cdni@ietfa.amsl.com>; Thu, 30 May 2013 10:24:17 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 0666821F9397 for <cdni@ietf.org>; Thu, 30 May 2013 10:24:12 -0700 (PDT)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id C68A132478F; Thu, 30 May 2013 19:24:11 +0200 (CEST)
Received: from PMEXCH51.intranet-paris.francetelecom.fr (unknown [10.100.76.23]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id AE1B14C05D; Thu, 30 May 2013 19:24:11 +0200 (CEST)
Received: from PMEXCB1D.intranet-paris.francetelecom.fr ([10.100.76.13]) by PMEXCH51.intranet-paris.francetelecom.fr ([10.100.76.23]) with mapi; Thu, 30 May 2013 19:24:11 +0200
From: <iuniana.oprescu@orange.com>
To: David Mandelberg <david@mandelberg.org>, "cdni@ietf.org" <cdni@ietf.org>
Date: Thu, 30 May 2013 19:24:10 +0200
Thread-Topic: [CDNi] non-repudiation questions
Thread-Index: Ac5dWiTQdWQWXE8tTKisPfXLE9xHeQAACNdA
Message-ID: <31963_1369934651_51A78B3B_31963_7151_1_8F0D2F5E4AAB7249BC7339A3E944DEDD20EC818EA1@PMEXCB1D.intranet-paris.francetelecom.fr>
References: <203799ab055aceac432998afe6bca638@mail.mandelberg.org>
In-Reply-To: <203799ab055aceac432998afe6bca638@mail.mandelberg.org>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.5.30.155423
Subject: Re: [CDNi] non-repudiation questions
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: Thu, 30 May 2013 17:24:21 -0000

Hello,

I'm in line with the two goals of non-repudiation for the logging data.=20=
=20

Cannot offer help for the private keys question.
-- iuniana

-----Message d'origine-----
De : cdni-bounces@ietf.org [mailto:cdni-bounces@ietf.org] De la part de Dav=
id Mandelberg
Envoy=E9 : jeudi 30 mai 2013 19:28
=C0 : cdni@ietf.org
Objet : [CDNi] non-repudiation questions

Hi,

What are the goals of non-repudiation of logging data? I've listed two poss=
ibilities below. Are those right? Is there anything else that people want n=
on-repudiation to do for them?

 * Audits: If a uCDN detects a problem that's supported by logging informat=
ion, the dCDN can't claim that they never supplied that logging information=
 or that the information was modified in transit.
 * Billing: Once a uCDN receives a log file, the dCDN can't claim that ther=
e are additional records that are missing from that file. (But they can sti=
ll add those records to a future log file.)

Also, how would dCDNs be willing to protect their private keys? If dCDNs do=
n't want to use hardware security modules, I'd recommend a solution that us=
es ephemeral keys.

--
David Eric Mandelberg / dseomn
http://david.mandelberg.org/
_______________________________________________
CDNi mailing list
CDNi@ietf.org
https://www.ietf.org/mailman/listinfo/cdni

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for message=
s that have been modified, changed or falsified.
Thank you.


From kleung@cisco.com  Fri May 31 08:35:43 2013
Return-Path: <kleung@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 98C5421F96E8 for <cdni@ietfa.amsl.com>; Fri, 31 May 2013 08:35:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 2TSxFjDA7Bxs for <cdni@ietfa.amsl.com>; Fri, 31 May 2013 08:35:38 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id BF83121F9385 for <cdni@ietf.org>; Fri, 31 May 2013 08:35:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2346; q=dns/txt; s=iport; t=1370014538; x=1371224138; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=FLndzjhpDQ8aqq1DJM6QnLsrUZy88IIbbxAXvaDMSiU=; b=QrEhJc/i0hvtsT2dTuPXLw5ol3+iSkx4uBbUdffARzgiUfXJQNnahdtj XUtkxA7JRHHiLIm4W8hZUB6/vaUZ5mDotuK+cg6cZ0dpQemSfleI5e9LN KfcZY2u+7KhuKhaMlcwW2EWjvNpyg83LB+m2VenbseYQ09ZJtqGe+JaDl Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiIGALzCqFGtJXHA/2dsb2JhbABagwkwQ4J5uy4NdRZtB4IjAQEBBCMRQw4EAgEIEQQBAQMCBh0DAgICMBQBBgEBBQMCBBMIAYgEBwWoUZIBgSaNSjgGgj0zYQOYZ5AXgw+BaiQZ
X-IronPort-AV: E=Sophos;i="4.87,779,1363132800"; d="scan'208";a="217249649"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-7.cisco.com with ESMTP; 31 May 2013 15:35:38 +0000
Received: from xhc-aln-x13.cisco.com (xhc-aln-x13.cisco.com [173.36.12.87]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r4VFZcsB003768 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <cdni@ietf.org>; Fri, 31 May 2013 15:35:38 GMT
Received: from xmb-aln-x03.cisco.com ([169.254.6.219]) by xhc-aln-x13.cisco.com ([173.36.12.87]) with mapi id 14.02.0318.004; Fri, 31 May 2013 10:35:37 -0500
From: "Kent Leung (kleung)" <kleung@cisco.com>
To: "cdni@ietf.org" <cdni@ietf.org>
Thread-Topic: New Version Notification for draft-leung-cdni-uri-signing-02.txt
Thread-Index: AQHOXhM4ha4dEQGnk0K+XA8WdCp9JpkfavFQ
Date: Fri, 31 May 2013 15:35:37 +0000
Message-ID: <CD85F32117029D4F9AEF48BDEF5536AB10266474@xmb-aln-x03.cisco.com>
References: <20130531152617.26809.88399.idtracker@ietfa.amsl.com>
In-Reply-To: <20130531152617.26809.88399.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.95.241]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: [CDNi] FW: New Version Notification for draft-leung-cdni-uri-signing-02.txt
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, 31 May 2013 15:35:43 -0000

SGkgZm9sa3MuICBXZSd2ZSBtYWRlIHNvbWUgdXBkYXRlcyBiYXNlZCBvbiB0aGUgV0cgZmVlZGJh
Y2sgYW5kIGludGVybmFsIGRpc2N1c3Npb25zLiBDb21tZW50cyBhcmUgd2VsY29tZS4gVGhhbmtz
LiANCg0KS2VudA0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogaW50ZXJuZXQt
ZHJhZnRzQGlldGYub3JnIFttYWlsdG86aW50ZXJuZXQtZHJhZnRzQGlldGYub3JnXSANClNlbnQ6
IEZyaWRheSwgTWF5IDMxLCAyMDEzIDg6MjYgQU0NClRvOiBSYXkgdmFuIEJyYW5kZW5idXJnOyBT
Y290dCBMZWlicmFuZDsgS2VudCBMZXVuZyAoa2xldW5nKTsgRnJhbmNvaXMgTGUgRmF1Y2hldXIg
KGZsZWZhdWNoKTsgQmlsbCBEb3duZXkNClN1YmplY3Q6IE5ldyBWZXJzaW9uIE5vdGlmaWNhdGlv
biBmb3IgZHJhZnQtbGV1bmctY2RuaS11cmktc2lnbmluZy0wMi50eHQNCg0KDQpBIG5ldyB2ZXJz
aW9uIG9mIEktRCwgZHJhZnQtbGV1bmctY2RuaS11cmktc2lnbmluZy0wMi50eHQNCmhhcyBiZWVu
IHN1Y2Nlc3NmdWxseSBzdWJtaXR0ZWQgYnkgS2VudCBMZXVuZyBhbmQgcG9zdGVkIHRvIHRoZSBJ
RVRGIHJlcG9zaXRvcnkuDQoNCkZpbGVuYW1lOgkgZHJhZnQtbGV1bmctY2RuaS11cmktc2lnbmlu
Zw0KUmV2aXNpb246CSAwMg0KVGl0bGU6CQkgVVJJIFNpZ25pbmcgZm9yIENETiBJbnRlcmNvbm5l
Y3Rpb24gKENETkkpDQpDcmVhdGlvbiBkYXRlOgkgMjAxMy0wNS0zMQ0KR3JvdXA6CQkgSW5kaXZp
ZHVhbCBTdWJtaXNzaW9uDQpOdW1iZXIgb2YgcGFnZXM6IDI5DQpVUkw6ICAgICAgICAgICAgIGh0
dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWxldW5nLWNkbmktdXJpLXNp
Z25pbmctMDIudHh0DQpTdGF0dXM6ICAgICAgICAgIGh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9y
Zy9kb2MvZHJhZnQtbGV1bmctY2RuaS11cmktc2lnbmluZw0KSHRtbGl6ZWQ6ICAgICAgICBodHRw
Oi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1sZXVuZy1jZG5pLXVyaS1zaWduaW5nLTAyDQpE
aWZmOiAgICAgICAgICAgIGh0dHA6Ly93d3cuaWV0Zi5vcmcvcmZjZGlmZj91cmwyPWRyYWZ0LWxl
dW5nLWNkbmktdXJpLXNpZ25pbmctMDINCg0KQWJzdHJhY3Q6DQogICBUaGlzIGRvY3VtZW50IGRl
c2NyaWJlcyBob3cgdGhlIGNvbmNlcHQgb2YgVVJJIHNpZ25pbmcgc3VwcG9ydHMgdGhlDQogICBj
b250ZW50IGFjY2VzcyBjb250cm9sIHJlcXVpcmVtZW50cyBvZiBDRE5JIGFuZCBwcm9wb3NlcyBh
IGNhbmRpZGF0ZQ0KICAgVVJJIHNpZ25pbmcgc2NoZW1lLg0KDQogICBUaGUgcHJvcG9zZWQgVVJJ
IHNpZ25pbmcgbWV0aG9kIHNwZWNpZmllcyB0aGUgaW5mb3JtYXRpb24gbmVlZGVkIHRvDQogICBi
ZSBpbmNsdWRlZCBpbiB0aGUgVVJJIGFuZCB0aGUgYWxnb3JpdGhtIHVzZWQgdG8gYXV0aG9yaXpl
IGFuZCB0bw0KICAgdmFsaWRhdGUgYWNjZXNzIHJlcXVlc3QgZm9yIHRoZSBjb250ZW50IHJlZmVy
ZW5jZWQgYnkgdGhlIFVSSS4gIFNvbWUNCiAgIG9mIHRoZSBpbmZvcm1hdGlvbiBtYXkgYmUgYWNj
ZXNzZWQgYnkgdGhlIENETiB2aWEgY29uZmlndXJhdGlvbiBvcg0KICAgQ0ROSSBtZXRhZGF0YS4N
Cg0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgIA0KDQoNClRoZSBJRVRGIFNlY3JldGFyaWF0DQoN
Cg==

From kleung@cisco.com  Fri May 31 08:50:10 2013
Return-Path: <kleung@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 8BE6D21F96EA for <cdni@ietfa.amsl.com>; Fri, 31 May 2013 08:50:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 BpI9v0Wy-ge5 for <cdni@ietfa.amsl.com>; Fri, 31 May 2013 08:50:05 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id CC46321F962B for <cdni@ietf.org>; Fri, 31 May 2013 08:50:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13234; q=dns/txt; s=iport; t=1370015400; x=1371225000; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=VKuinHM5xl89p1MqZGRqS0pLFDyS+8DL/KcMDqxPCFg=; b=YVNEE9+7Mry5t1w8lWNVhjpg9z5/JX8SnYY9aShQxnh2hRm5lqfXmsLz RLS2ENVgBSe57BDOCRa4jcWMxj3UaIkhIrWPs0JYp9uu8GNdXug1f/7SK AMU51ok0DxAebw+2JNCIR9pEiAymMcgoCRZSGrrBIS1doEkp6xg3cX4W0 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlUFAKHFqFGtJXG8/2dsb2JhbABagkVEML5ugQIWdIIjAQEBBC1MEAIBCBEDAQEBCx0HMhQJCAIEAQ0FCBOHcrpdjnANExEGAYJ2YQOofoMPgic
X-IronPort-AV: E=Sophos;i="4.87,779,1363132800";  d="scan'208,217";a="217349380"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-4.cisco.com with ESMTP; 31 May 2013 15:49:59 +0000
Received: from xhc-aln-x09.cisco.com (xhc-aln-x09.cisco.com [173.36.12.83]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id r4VFnxRf030446 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 31 May 2013 15:49:59 GMT
Received: from xmb-aln-x03.cisco.com ([169.254.6.219]) by xhc-aln-x09.cisco.com ([173.36.12.83]) with mapi id 14.02.0318.004; Fri, 31 May 2013 10:49:58 -0500
From: "Kent Leung (kleung)" <kleung@cisco.com>
To: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>, Daryl Malas <d.malas@cablelabs.com>
Thread-Topic: [CDNi] Chair review of Requirements draft
Thread-Index: AQHOWL4ol8g/hXc8EEqlADDdC7rE15ka9ZGAgAD0boCAA5Fg8A==
Date: Fri, 31 May 2013 15:49:58 +0000
Message-ID: <CD85F32117029D4F9AEF48BDEF5536AB102664A7@xmb-aln-x03.cisco.com>
References: <CD85F32117029D4F9AEF48BDEF5536AB10265561@xmb-aln-x03.cisco.com> <E3FAB1F4F41F3A45B287E8D9C53522FD472ACB5B@PACDCEXMB05.cable.comcast.com>
In-Reply-To: <E3FAB1F4F41F3A45B287E8D9C53522FD472ACB5B@PACDCEXMB05.cable.comcast.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.95.241]
Content-Type: multipart/alternative; boundary="_000_CD85F32117029D4F9AEF48BDEF5536AB102664A7xmbalnx03ciscoc_"
MIME-Version: 1.0
Cc: "cdni@ietf.org" <cdni@ietf.org>
Subject: Re: [CDNi] Chair review of Requirements draft
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, 31 May 2013 15:50:11 -0000

--_000_CD85F32117029D4F9AEF48BDEF5536AB102664A7xmbalnx03ciscoc_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Yiu. This looks good to me.

Kent

From: Lee, Yiu [mailto:Yiu_Lee@Cable.Comcast.com]
Sent: Tuesday, May 28, 2013 9:20 PM
To: Kent Leung (kleung); Daryl Malas
Cc: cdni@ietf.org
Subject: Re: [CDNi] Chair review of Requirements draft

Hi Kent and Darly,

I want to make a slight change of the abstract to make it even more objecti=
ve:

"Content Delivery Networks (CDNs) are frequently used for content delivery.=
 As a result of significant growth in content delivered over IP networks, e=
xisting CDN providers are scaling up their infrastructure. Many Network Ser=
vice Providers and Enterprise Service Providers are also deploying their ow=
n CDNs. To deliver contents from the Content Service Protect (CSP) to end u=
sers, the contents may traverse across multiple CDNs. This creates a need f=
or interconnecting (previously) standalone CDNs so that they can collective=
ly act as a single delivery platform from the CSP to the end users.

The goal of this memo is to outline the requirements for the CDNI working g=
roup."

What do you guys think?

Thanks,
Yiu

From: "Kent Leung (kleung)" <kleung@cisco.com<mailto:kleung@cisco.com>>
Date: Tuesday, May 28, 2013 4:58 PM
To: Daryl Malas <D.Malas@cablelabs.com<mailto:D.Malas@cablelabs.com>>, "Yiu=
 L. LEE" <yiu_lee@cable.comcast.com<mailto:yiu_lee@cable.comcast.com>>
Cc: "cdni@ietf.org<mailto:cdni@ietf.org>" <cdni@ietf.org<mailto:cdni@ietf.o=
rg>>
Subject: RE: [CDNi] Chair review of Requirements draft

KL> Just want to clarify. Is this text correct for the Abstract section?

"Content Delivery Networks (CDNs) are frequently used for large-scale conte=
nt delivery. As a result of the significant growth in content delivered ove=
r IP networks, existing CDN providers are scaling up their infrastructure a=
nd many Network Service Providers and Enterprise Service Providers are depl=
oying their own CDNs. Subject to the policy of the CSP, it is generally des=
irable that a given item of content can be delivered to an end user regardl=
ess of that end user's location or attachment network.  This creates a need=
 for interconnecting (previously) standalone CDNs so they can interoperate =
and collectively behave as a single delivery infrastructure. The Content Di=
stribution Network Interconnection (CDNI) working group has been chartered =
to develop an interoperable and scalable solution for such CDN interconnect=
ion.

The goal of the present document is to outline the requirements for the sol=
ution and interfaces to be specified by the CDNI working group."

--_000_CD85F32117029D4F9AEF48BDEF5536AB102664A7xmbalnx03ciscoc_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi Yiu. This looks good t=
o me.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Kent<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Lee, Yiu=
 [mailto:Yiu_Lee@Cable.Comcast.com]
<br>
<b>Sent:</b> Tuesday, May 28, 2013 9:20 PM<br>
<b>To:</b> Kent Leung (kleung); Daryl Malas<br>
<b>Cc:</b> cdni@ietf.org<br>
<b>Subject:</b> Re: [CDNi] Chair review of Requirements draft<o:p></o:p></s=
pan></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">Hi Kent and Darly,<o:p></o:=
p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">I want to make a slight cha=
nge of the abstract to make it even more objective:<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">&quot;Content Delivery Netw=
orks (CDNs) are frequently used for content delivery. As a result of signif=
icant growth in content delivered over IP networks, existing
 CDN providers are scaling up their infrastructure. Many Network Service Pr=
oviders and Enterprise Service Providers are also deploying their own CDNs.=
 To deliver contents from the Content Service Protect (CSP) to end users, t=
he contents may traverse across
 multiple CDNs. This creates a need for interconnecting (previously) standa=
lone CDNs so that they can collectively act as a single delivery platform f=
rom the CSP to the end users.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">The goal of this memo is to=
 outline the requirements for the CDNI working group.&quot;<o:p></o:p></spa=
n></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">What do you guys think?<o:p=
></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">Thanks,<o:p></o:p></span></=
p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">Yiu<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:black">From:
</span></b><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,=
&quot;sans-serif&quot;;color:black">&quot;Kent Leung (kleung)&quot; &lt;<a =
href=3D"mailto:kleung@cisco.com">kleung@cisco.com</a>&gt;<br>
<b>Date: </b>Tuesday, May 28, 2013 4:58 PM<br>
<b>To: </b>Daryl Malas &lt;<a href=3D"mailto:D.Malas@cablelabs.com">D.Malas=
@cablelabs.com</a>&gt;, &quot;Yiu L. LEE&quot; &lt;<a href=3D"mailto:yiu_le=
e@cable.comcast.com">yiu_lee@cable.comcast.com</a>&gt;<br>
<b>Cc: </b>&quot;<a href=3D"mailto:cdni@ietf.org">cdni@ietf.org</a>&quot; &=
lt;<a href=3D"mailto:cdni@ietf.org">cdni@ietf.org</a>&gt;<br>
<b>Subject: </b>RE: [CDNi] Chair review of Requirements draft<o:p></o:p></s=
pan></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<p class=3D"MsoNormal" style=3D"orphans: 2;text-align:-webkit-auto;widows: =
2;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacin=
g:0px">
<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:#1F497D">KL&gt; Just want to clarify. Is this text correc=
t for the Abstract section?</span><span style=3D"color:black"><o:p></o:p></=
span></p>
<p class=3D"MsoNormal" style=3D"orphans: 2;text-align:-webkit-auto;widows: =
2;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacin=
g:0px">
<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black"><o:p></=
o:p></span></p>
<p class=3D"MsoNormal" style=3D"orphans: 2;text-align:-webkit-auto;widows: =
2;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacin=
g:0px">
<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:#1F497D">&#8220;Content Delivery Networks (CDNs) are freq=
uently used for large-scale content delivery. As a result of the significan=
t growth in content delivered over IP networks, existing CDN
 providers are scaling up their infrastructure and many Network Service Pro=
viders and Enterprise Service Providers are deploying their own CDNs. Subje=
ct to the policy of the CSP, it is generally desirable that a given item of=
 content can be delivered to an
 end user regardless of that end user's location or attachment network.&nbs=
p; This creates a need for interconnecting (previously) standalone CDNs so =
they can interoperate and collectively behave as a single delivery infrastr=
ucture. The Content Distribution Network
 Interconnection (CDNI) working group has been chartered to develop an inte=
roperable and scalable solution for such CDN interconnection.</span><span s=
tyle=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"orphans: 2;text-align:-webkit-auto;widows: =
2;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacin=
g:0px">
<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black"><o:p></=
o:p></span></p>
<p class=3D"MsoNormal" style=3D"orphans: 2;text-align:-webkit-auto;widows: =
2;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacin=
g:0px">
<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:#1F497D">The goal of the present document is to outline t=
he requirements for the solution and interfaces to be specified by the CDNI=
 working group.&#8221;</span><span style=3D"color:black"><o:p></o:p></span>=
</p>
</div>
</body>
</html>

--_000_CD85F32117029D4F9AEF48BDEF5536AB102664A7xmbalnx03ciscoc_--

From internet-drafts@ietf.org  Fri May 31 09:12:29 2013
Return-Path: <internet-drafts@ietf.org>
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 822A621F98AC; Fri, 31 May 2013 09:12:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.001
X-Spam-Level: 
X-Spam-Status: No, score=-100.001 tagged_above=-999 required=5 tests=[NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 UTa23o4fRG6S; Fri, 31 May 2013 09:12:29 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BAA4221F9732; Fri, 31 May 2013 09:12:28 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.50
Message-ID: <20130531161228.29335.28647.idtracker@ietfa.amsl.com>
Date: Fri, 31 May 2013 09:12:28 -0700
Cc: cdni@ietf.org
Subject: [CDNi] I-D Action: draft-ietf-cdni-requirements-07.txt
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, 31 May 2013 16:12:29 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Content Delivery Networks Interconnection=
 Working Group of the IETF.

	Title           : Content Distribution Network Interconnection (CDNI) Requ=
irements
	Author(s)       : Kent Leung
                          Yiu Lee
	Filename        : draft-ietf-cdni-requirements-07.txt
	Pages           : 24
	Date            : 2013-05-31

Abstract:
   Content Delivery Networks (CDNs) are frequently used for content
   delivery.  As a result of significant growth in content delivered
   over IP networks, existing CDN providers are scaling up their
   infrastructure.  Many Network Service Providers and Enterprise
   Service Providers are also deploying their own CDNs.  To deliver
   contents from the Content Service Protect (CSP) to end users, the
   contents may traverse across multiple CDNs.  This creates a need for
   interconnecting (previously) standalone CDNs so that they can
   collectively act as a single delivery platform from the CSP to the
   end users.

   The goal of the present document is to outline the requirements for
   the solution and interfaces to be specified by the CDNI working
   group.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-cdni-requirements

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-cdni-requirements-07

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cdni-requirements-07


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From internet-drafts@ietf.org  Fri May 31 09:52:34 2013
Return-Path: <internet-drafts@ietf.org>
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 BB7A721F96F5; Fri, 31 May 2013 09:52:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.518
X-Spam-Level: 
X-Spam-Status: No, score=-99.518 tagged_above=-999 required=5 tests=[AWL=0.483, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 6T8C8ApMsUrw; Fri, 31 May 2013 09:52:34 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 387C721F8667; Fri, 31 May 2013 09:52:34 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.50
Message-ID: <20130531165234.2329.225.idtracker@ietfa.amsl.com>
Date: Fri, 31 May 2013 09:52:34 -0700
Cc: cdni@ietf.org
Subject: [CDNi] I-D Action: draft-ietf-cdni-logging-03.txt
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, 31 May 2013 16:52:35 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Content Delivery Networks Interconnection=
 Working Group of the IETF.

	Title           : CDNI Logging Interface
	Author(s)       : Gilles Bertrand
                          Iuniana Oprescu
                          Francois Le Faucheur
                          Roy Peterkofsky
	Filename        : draft-ietf-cdni-logging-03.txt
	Pages           : 37
	Date            : 2013-05-31

Abstract:
   This memo specifies the Logging interface between a downstream CDN
   (dCDN) and an upstream CDN (uCDN) that are interconnected as per the
   CDN Interconnection (CDNI) framework.  First, it describes a
   reference model for CDNI logging.  Then, it specifies the CDNI
   Logging File format and the actual protocol for exchange of CDNI
   Logging Files.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-cdni-logging

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-cdni-logging-03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cdni-logging-03


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From flefauch@cisco.com  Fri May 31 09:55:13 2013
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 D6A7C21F8763 for <cdni@ietfa.amsl.com>; Fri, 31 May 2013 09:55:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.999
X-Spam-Level: 
X-Spam-Status: No, score=-7.999 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, 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 2Gs+V7l3BHGa for <cdni@ietfa.amsl.com>; Fri, 31 May 2013 09:55:09 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id D59DD21F8609 for <cdni@ietf.org>; Fri, 31 May 2013 09:55:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7596; q=dns/txt; s=iport; t=1370019308; x=1371228908; h=from:to:subject:date:message-id:references:mime-version; bh=YAAtjTlC69zuWOOCQcMQ+LUpEwGJQlZcagDfZRxiMY0=; b=Mx/o9J+f+BqSUNku9W7HXZ50TvHqk0G/Kyz8fWKefctwE3esKLjwYFLB vfNA2wZKAloCTjidpgd01su5HYw4ZC4DcmmB/A8ncf+TswTaBdJQxBEds xwx9AxvXb7/hhOmSaHd+NT5mT25ODLq1L11FuRjU8YQIZ2FQvm0lhs4HS 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlUFAIzVqFGtJXG+/2dsb2JhbABagwkwQ74rgQIWdIIjAQEBBAEBAWsbAgEZAwECCx0HJwsUBwIIAgQTCAGIBAcFulKOcCANCgeCcGEDmGeQF4MPgic
X-IronPort-AV: E=Sophos;i="4.87,780,1363132800";  d="scan'208,217";a="217098519"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-1.cisco.com with ESMTP; 31 May 2013 16:55:08 +0000
Received: from xhc-aln-x15.cisco.com (xhc-aln-x15.cisco.com [173.36.12.89]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id r4VGt8aF010109 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <cdni@ietf.org>; Fri, 31 May 2013 16:55:08 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.56]) by xhc-aln-x15.cisco.com ([173.36.12.89]) with mapi id 14.02.0318.004; Fri, 31 May 2013 11:55:07 -0500
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "<cdni@ietf.org>" <cdni@ietf.org>
Thread-Topic: [CDNi] I-D Action: draft-ietf-cdni-logging-03.txt
Thread-Index: AQHOXh9FrhN8AbuP20evX8mt2B858g==
Date: Fri, 31 May 2013 16:55:06 +0000
Message-ID: <FC236DA6F2DA77449EF2D02DF4471A8D63D076@xmb-rcd-x10.cisco.com>
References: <20130531165234.2329.225.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.55.161.201]
Content-Type: multipart/alternative; boundary="_000_FC236DA6F2DA77449EF2D02DF4471A8D63D076xmbrcdx10ciscocom_"
MIME-Version: 1.0
Subject: [CDNi] Fwd:  I-D Action: draft-ietf-cdni-logging-03.txt
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, 31 May 2013 16:55:14 -0000

--_000_FC236DA6F2DA77449EF2D02DF4471A8D63D076xmbrcdx10ciscocom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Folks,

Just posted a new version of cdni-logging that reflects the discussion from=
 this weeks's informal meeting.
We'll continue discussion next Wed during the 2nd informal meeting on CDNI =
Logging.

Cheers

Francois


Begin forwarded message:

From: <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>>
Subject: [CDNi] I-D Action: draft-ietf-cdni-logging-03.txt
Date: 31 May 2013 18:52:34 CEST
To: <i-d-announce@ietf.org<mailto:i-d-announce@ietf.org>>
Cc: <cdni@ietf.org<mailto:cdni@ietf.org>>


A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
This draft is a work item of the Content Delivery Networks Interconnection =
Working Group of the IETF.

Title           : CDNI Logging Interface
Author(s)       : Gilles Bertrand
                         Iuniana Oprescu
                         Francois Le Faucheur
                         Roy Peterkofsky
Filename        : draft-ietf-cdni-logging-03.txt
Pages           : 37
Date            : 2013-05-31

Abstract:
  This memo specifies the Logging interface between a downstream CDN
  (dCDN) and an upstream CDN (uCDN) that are interconnected as per the
  CDN Interconnection (CDNI) framework.  First, it describes a
  reference model for CDNI logging.  Then, it specifies the CDNI
  Logging File format and the actual protocol for exchange of CDNI
  Logging Files.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-cdni-logging

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-cdni-logging-03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cdni-logging-03


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
CDNi mailing list
CDNi@ietf.org
https://www.ietf.org/mailman/listinfo/cdni


--_000_FC236DA6F2DA77449EF2D02DF4471A8D63D076xmbrcdx10ciscocom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <522353BA62ADE04F84FFFDAA4069430F@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
Folks,
<div><br>
</div>
<div>Just posted a new version of cdni-logging that reflects the discussion=
 from this weeks's informal meeting.</div>
<div>We'll continue discussion next Wed during the 2nd informal meeting on =
CDNI Logging.</div>
<div><br>
</div>
<div>Cheers</div>
<div><br>
</div>
<div>Francois</div>
<div><br>
<div><br>
<div>Begin forwarded message:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;">
<span style=3D"font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, =
0, 1.0);"><b>From:
</b></span><span style=3D"font-family:'Helvetica'; font-size:medium;">&lt;<=
a href=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a>&gt;=
<br>
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;">
<span style=3D"font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, =
0, 1.0);"><b>Subject:
</b></span><span style=3D"font-family:'Helvetica'; font-size:medium;"><b>[C=
DNi] I-D Action: draft-ietf-cdni-logging-03.txt</b><br>
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;">
<span style=3D"font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, =
0, 1.0);"><b>Date:
</b></span><span style=3D"font-family:'Helvetica'; font-size:medium;">31 Ma=
y 2013 18:52:34 CEST<br>
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;">
<span style=3D"font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, =
0, 1.0);"><b>To:
</b></span><span style=3D"font-family:'Helvetica'; font-size:medium;">&lt;<=
a href=3D"mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</a>&gt;<br>
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;">
<span style=3D"font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, =
0, 1.0);"><b>Cc:
</b></span><span style=3D"font-family:'Helvetica'; font-size:medium;">&lt;<=
a href=3D"mailto:cdni@ietf.org">cdni@ietf.org</a>&gt;<br>
</span></div>
<br>
<div><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
This draft is a work item of the Content Delivery Networks Interconnection =
Working Group of the IETF.<br>
<br>
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>Title &nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: CDNI Logging Inter=
face<br>
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>Author(s) &=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: Gilles Bertrand<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
Iuniana Oprescu<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
Francois Le Faucheur<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
Roy Peterkofsky<br>
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>Filename &n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: draft-ietf-cdni-logging-03.txt<br=
>
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>Pages &nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: 37<br>
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>Date &nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: 2013-05-31<br=
>
<br>
Abstract:<br>
&nbsp;&nbsp;This memo specifies the Logging interface between a downstream =
CDN<br>
&nbsp;&nbsp;(dCDN) and an upstream CDN (uCDN) that are interconnected as pe=
r the<br>
&nbsp;&nbsp;CDN Interconnection (CDNI) framework. &nbsp;First, it describes=
 a<br>
&nbsp;&nbsp;reference model for CDNI logging. &nbsp;Then, it specifies the =
CDNI<br>
&nbsp;&nbsp;Logging File format and the actual protocol for exchange of CDN=
I<br>
&nbsp;&nbsp;Logging Files.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-cdni-logging">https:=
//datatracker.ietf.org/doc/draft-ietf-cdni-logging</a><br>
<br>
There's also a htmlized version available at:<br>
http://tools.ietf.org/html/draft-ietf-cdni-logging-03<br>
<br>
A diff from the previous version is available at:<br>
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cdni-logging-03<br>
<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
ftp://ftp.ietf.org/internet-drafts/<br>
<br>
_______________________________________________<br>
CDNi mailing list<br>
CDNi@ietf.org<br>
https://www.ietf.org/mailman/listinfo/cdni<br>
</div>
</blockquote>
</div>
<br>
</div>
</body>
</html>

--_000_FC236DA6F2DA77449EF2D02DF4471A8D63D076xmbrcdx10ciscocom_--

From flefauch@cisco.com  Fri May 31 09:56:31 2013
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 DA66621F8763 for <cdni@ietfa.amsl.com>; Fri, 31 May 2013 09:56:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.999
X-Spam-Level: 
X-Spam-Status: No, score=-7.999 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, 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 t4ZeaZGSE-zJ for <cdni@ietfa.amsl.com>; Fri, 31 May 2013 09:56:27 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id DB84D21F8616 for <cdni@ietf.org>; Fri, 31 May 2013 09:56:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9135; q=dns/txt; s=iport; t=1370019387; x=1371228987; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=OoajvzElPAWTdMuvED1n0dbTqoXjrzWWDN5c+tRIlI0=; b=MBEyHwfr1zixGiD+Sioor+Da3Nqy9PDSB/8FLR9qiuOZgf6APiqLnDhR wAEJbUsFN0V7OJV34fBZh5P1wYpBOO1oqknZmf25e/eVhlcnSF4oPv9u/ EYFrl24uQohzFjiTvV8vd3fEsTl5Sj0f1Krp3QCFxJ61nU2SIRImTc0Yl U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArgNAADWqFGtJXG8/2dsb2JhbABagwkwQ4QXsVmIO4ECFm0HgiMBAQEEAQEBaxsCAQgRAwECCx0HJwsUCQgCBBMIAYgEBwW6Uo5wIA0KAQaCcGEDmGeQF4MPgic
X-IronPort-AV: E=Sophos;i="4.87,780,1363132800";  d="scan'208,217";a="217306872"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-6.cisco.com with ESMTP; 31 May 2013 16:56:24 +0000
Received: from xhc-aln-x14.cisco.com (xhc-aln-x14.cisco.com [173.36.12.88]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id r4VGuNwf011087 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <cdni@ietf.org>; Fri, 31 May 2013 16:56:23 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.56]) by xhc-aln-x14.cisco.com ([173.36.12.88]) with mapi id 14.02.0318.004; Fri, 31 May 2013 11:56:23 -0500
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "cdni@ietf.org" <cdni@ietf.org>
Thread-Topic: [CDNi]  I-D Action: draft-ietf-cdni-logging-03.txt
Thread-Index: AQHOXh/HfLhmn1mZ00Gc5rXgveDgCA==
Date: Fri, 31 May 2013 16:56:23 +0000
Message-ID: <FC236DA6F2DA77449EF2D02DF4471A8D63D0C2@xmb-rcd-x10.cisco.com>
References: <20130531165234.2329.225.idtracker@ietfa.amsl.com> <FC236DA6F2DA77449EF2D02DF4471A8D63D076@xmb-rcd-x10.cisco.com>
In-Reply-To: <FC236DA6F2DA77449EF2D02DF4471A8D63D076@xmb-rcd-x10.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.55.161.201]
Content-Type: multipart/alternative; boundary="_000_FC236DA6F2DA77449EF2D02DF4471A8D63D0C2xmbrcdx10ciscocom_"
MIME-Version: 1.0
Subject: Re: [CDNi] I-D Action: draft-ietf-cdni-logging-03.txt
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, 31 May 2013 16:56:32 -0000

--_000_FC236DA6F2DA77449EF2D02DF4471A8D63D0C2xmbrcdx10ciscocom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


On 31 May 2013, at 18:55, Francois Le Faucheur (flefauch) <flefauch@cisco.c=
om<mailto:flefauch@cisco.com>> wrote:

Folks,

Just posted a new version of cdni-logging that reflects the discussion from=
 this weeks's informal meeting.

BTW, Diff from previous version:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cdni-logging-03


We'll continue discussion next Wed during the 2nd informal meeting on CDNI =
Logging.

Cheers

Francois


Begin forwarded message:

From: <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>>
Subject: [CDNi] I-D Action: draft-ietf-cdni-logging-03.txt
Date: 31 May 2013 18:52:34 CEST
To: <i-d-announce@ietf.org<mailto:i-d-announce@ietf.org>>
Cc: <cdni@ietf.org<mailto:cdni@ietf.org>>


A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
This draft is a work item of the Content Delivery Networks Interconnection =
Working Group of the IETF.

Title           : CDNI Logging Interface
Author(s)       : Gilles Bertrand
                         Iuniana Oprescu
                         Francois Le Faucheur
                         Roy Peterkofsky
Filename        : draft-ietf-cdni-logging-03.txt
Pages           : 37
Date            : 2013-05-31

Abstract:
  This memo specifies the Logging interface between a downstream CDN
  (dCDN) and an upstream CDN (uCDN) that are interconnected as per the
  CDN Interconnection (CDNI) framework.  First, it describes a
  reference model for CDNI logging.  Then, it specifies the CDNI
  Logging File format and the actual protocol for exchange of CDNI
  Logging Files.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-cdni-logging

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-cdni-logging-03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cdni-logging-03


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
CDNi mailing list
CDNi@ietf.org<mailto:CDNi@ietf.org>
https://www.ietf.org/mailman/listinfo/cdni

_______________________________________________
CDNi mailing list
CDNi@ietf.org<mailto:CDNi@ietf.org>
https://www.ietf.org/mailman/listinfo/cdni


--_000_FC236DA6F2DA77449EF2D02DF4471A8D63D0C2xmbrcdx10ciscocom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <02B581242FA0DF40995C77297C7DFFD7@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<br>
<div>
<div>On 31 May 2013, at 18:55, Francois Le Faucheur (flefauch) &lt;<a href=
=3D"mailto:flefauch@cisco.com">flefauch@cisco.com</a>&gt; wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; ">
Folks,
<div><br>
</div>
<div>Just posted a new version of cdni-logging that reflects the discussion=
 from this weeks's informal meeting.</div>
</div>
</blockquote>
<div><br>
</div>
<div>BTW,&nbsp;Diff from previous version:</div>
<div><a href=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cdni-logging-=
03">http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cdni-logging-03</a></div>
<div><br>
</div>
<br>
<blockquote type=3D"cite">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; ">
<div>We'll continue discussion next Wed during the 2nd informal meeting on =
CDNI Logging.</div>
<div><br>
</div>
<div>Cheers</div>
<div><br>
</div>
<div>Francois</div>
<div><br>
<div><br>
<div>Begin forwarded message:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;">
<span style=3D"font-family: Helvetica; font-size: medium; "><b>From: </b></=
span><span style=3D"font-family:'Helvetica'; font-size:medium;">&lt;<a href=
=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a>&gt;<br>
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;">
<span style=3D"font-family: Helvetica; font-size: medium; "><b>Subject: </b=
></span><span style=3D"font-family:'Helvetica'; font-size:medium;"><b>[CDNi=
] I-D Action: draft-ietf-cdni-logging-03.txt</b><br>
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;">
<span style=3D"font-family: Helvetica; font-size: medium; "><b>Date: </b></=
span><span style=3D"font-family:'Helvetica'; font-size:medium;">31 May 2013=
 18:52:34 CEST<br>
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;">
<span style=3D"font-family: Helvetica; font-size: medium; "><b>To: </b></sp=
an><span style=3D"font-family:'Helvetica'; font-size:medium;">&lt;<a href=
=3D"mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</a>&gt;<br>
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;">
<span style=3D"font-family: Helvetica; font-size: medium; "><b>Cc: </b></sp=
an><span style=3D"font-family:'Helvetica'; font-size:medium;">&lt;<a href=
=3D"mailto:cdni@ietf.org">cdni@ietf.org</a>&gt;<br>
</span></div>
<br>
<div><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
This draft is a work item of the Content Delivery Networks Interconnection =
Working Group of the IETF.<br>
<br>
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>Title &nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: CDNI Logging Inter=
face<br>
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>Author(s) &=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: Gilles Bertrand<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
Iuniana Oprescu<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
Francois Le Faucheur<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
Roy Peterkofsky<br>
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>Filename &n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: draft-ietf-cdni-logging-03.txt<br=
>
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>Pages &nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: 37<br>
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>Date &nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: 2013-05-31<br=
>
<br>
Abstract:<br>
&nbsp;&nbsp;This memo specifies the Logging interface between a downstream =
CDN<br>
&nbsp;&nbsp;(dCDN) and an upstream CDN (uCDN) that are interconnected as pe=
r the<br>
&nbsp;&nbsp;CDN Interconnection (CDNI) framework. &nbsp;First, it describes=
 a<br>
&nbsp;&nbsp;reference model for CDNI logging. &nbsp;Then, it specifies the =
CDNI<br>
&nbsp;&nbsp;Logging File format and the actual protocol for exchange of CDN=
I<br>
&nbsp;&nbsp;Logging Files.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-cdni-logging">https:=
//datatracker.ietf.org/doc/draft-ietf-cdni-logging</a><br>
<br>
There's also a htmlized version available at:<br>
<a href=3D"http://tools.ietf.org/html/draft-ietf-cdni-logging-03">http://to=
ols.ietf.org/html/draft-ietf-cdni-logging-03</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cdni-logging-03">h=
ttp://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cdni-logging-03</a><br>
<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/">ftp://ftp.ietf.org/internet=
-drafts/</a><br>
<br>
_______________________________________________<br>
CDNi mailing list<br>
<a href=3D"mailto:CDNi@ietf.org">CDNi@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/cdni">https://www.ietf.org=
/mailman/listinfo/cdni</a><br>
</div>
</blockquote>
</div>
<br>
</div>
</div>
_______________________________________________<br>
CDNi mailing list<br>
<a href=3D"mailto:CDNi@ietf.org">CDNi@ietf.org</a><br>
https://www.ietf.org/mailman/listinfo/cdni<br>
</blockquote>
</div>
<br>
</body>
</html>

--_000_FC236DA6F2DA77449EF2D02DF4471A8D63D0C2xmbrcdx10ciscocom_--

From ietfdbh@comcast.net  Fri May 31 10:29:35 2013
Return-Path: <ietfdbh@comcast.net>
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 9ACEC21F85C3 for <cdni@ietfa.amsl.com>; Fri, 31 May 2013 10:29:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.838
X-Spam-Level: 
X-Spam-Status: No, score=-97.838 tagged_above=-999 required=5 tests=[FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 yvOSf6DECaWB for <cdni@ietfa.amsl.com>; Fri, 31 May 2013 10:29:31 -0700 (PDT)
Received: from qmta06.westchester.pa.mail.comcast.net (qmta06.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:56]) by ietfa.amsl.com (Postfix) with ESMTP id C8CF921F85BF for <cdni@ietf.org>; Fri, 31 May 2013 10:29:27 -0700 (PDT)
Received: from omta05.westchester.pa.mail.comcast.net ([76.96.62.43]) by qmta06.westchester.pa.mail.comcast.net with comcast id idZB1l0060vyq2s56hVSyW; Fri, 31 May 2013 17:29:26 +0000
Received: from JV6RVH1 ([67.189.237.137]) by omta05.westchester.pa.mail.comcast.net with comcast id ihVS1l00h2yZEBF3RhVSR6; Fri, 31 May 2013 17:29:26 +0000
From: "ietfdbh" <ietfdbh@comcast.net>
To: <cdni@ietf.org>
References: <20130531165234.2329.225.idtracker@ietfa.amsl.com>
In-Reply-To: <20130531165234.2329.225.idtracker@ietfa.amsl.com>
Date: Fri, 31 May 2013 13:29:10 -0400
Message-ID: <005b01ce5e24$5ca824c0$15f86e40$@comcast.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHO/PSwZTUauOhSXgGYHCbWDtWfNZkeSm4A
Content-Language: en-us
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1370021366; bh=H7jyC7LJJuD58qM7k3mesM3OSGDWyV4x0xOxQt4Ybis=; h=Received:Received:From:To:Subject:Date:Message-ID:MIME-Version: Content-Type; b=owb+fJIU+pSCcceG3ApPlthrAqZq49f/PiPJGogKJU1hF874PJC/j5fDBDNx9LN6k Uiw0ZIsIGsbBlpeJKN/orrpI7S6LE8ht+VdtESrj73jjasgB2AkhDQ7CB1y+sXNvQK 4++LQFSxAD+DJ8nPGkqYg8MDW4CujStJraBAowtZ2P0a79RpJP0vt8CaKe1AgV8r3O tDNMiUdlWhyzm2tl8TRbASUcLxjNB5XAROgexaUlfeaXzvCAePlRUTotkc5wu5nym5 DAQPhCSbiOGLsiptiuzAk9TsUafVXS+8h8xoj7aflXqLX/iloDE945cLpNJqCUOLib vyXxh8IVnvhmQ==
Subject: Re: [CDNi] I-D Action: draft-ietf-cdni-logging-03.txt
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, 31 May 2013 17:29:35 -0000

Hi,

I saw this announcement and was curious about whether you were reusing
existing standards, so I took a quick look (not a thorough review). A =
couple
comments:

1) in section 2.2.1, there is text "may not keep more logs";
This is ambiguous - does this mean "MAY NOT keep more logs" or "might =
not
keep more logs"?

2) syslog and snmp are both traditionally UDP-based, and lack
transport-provided congestion control.
If you use syslog and/or snmp traps (as compared to Informs), there is
typically no application-level ack, something you might want especially =
for
accounting/billing purposes.
You might want to explicitly check the TLS variations for these, for
security and congestion control reasons.
You might want to explicitly check the syslog-sign standard, and SNMP
Informs, for their acknowledgement capabilities (although Inform only =
says
"I got it", without any guarantee that the content of the notification =
is
processed).

3) You might want to add ipfix, radius, and diameter to the list of
candidates. These might be suitable choices for some environments, =
possibly
with CDNI-specific extensions. Some discussion of radius/tacacs+, and =
snmp
has been done in rfc2975 - definitely dated material now, but it might
mention some things to consider. I do expect that the WG has far more
experience with these issues vis-=E0-vis CDNI than were common at the =
time of
rfc2975 ;-)

David Harrington
ietfdbh@comcast.net
+1-603-828-1401

-----Original Message-----
From: i-d-announce-bounces@ietf.org =
[mailto:i-d-announce-bounces@ietf.org]
On Behalf Of internet-drafts@ietf.org
Sent: Friday, May 31, 2013 12:53 PM
To: i-d-announce@ietf.org
Cc: cdni@ietf.org
Subject: I-D Action: draft-ietf-cdni-logging-03.txt


A New Internet-Draft is available from the on-line Internet-Drafts
directories.
 This draft is a work item of the Content Delivery Networks =
Interconnection
Working Group of the IETF.

	Title           : CDNI Logging Interface
	Author(s)       : Gilles Bertrand
                          Iuniana Oprescu
                          Francois Le Faucheur
                          Roy Peterkofsky
	Filename        : draft-ietf-cdni-logging-03.txt
	Pages           : 37
	Date            : 2013-05-31

Abstract:
   This memo specifies the Logging interface between a downstream CDN
   (dCDN) and an upstream CDN (uCDN) that are interconnected as per the
   CDN Interconnection (CDNI) framework.  First, it describes a
   reference model for CDNI logging.  Then, it specifies the CDNI
   Logging File format and the actual protocol for exchange of CDNI
   Logging Files.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-cdni-logging

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-cdni-logging-03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cdni-logging-03


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html or
ftp://ftp.ietf.org/ietf/1shadow-sites.txt

