Subject: Re: [CDNi] CDNI Logging - 2 proposals for scoping of the first version of the CDNI interfaces

From: "Francois Le Faucheur (flefauch)" <[email-masked]>
Date: Mon, 14 Jan 2013 13:38:26 +0000

Folks,
Since we haven't heard any disagreement with the two proposals below, we'll move ahead with those.
Cheers
Francois

On 20 Dec 2012, at 11:45, Francois Le Faucheur (flefauch) <[email-masked]> wrote:

> Folks,
> 
> (speaking as an individual)
> 
> As announced earlier, a bunch of us (1) interested in CDNI Logging had an informal discussion around two aspects of CDNI Logging Yesterday. We converged on two proposals detailed below for which we are solliciting comments. Please review those and pass on the comments you may have, so the WG can make a decision on those.
> 
> 
> Proposal 1:
> ======== 
> 	o Aim to support in the first version of the CDNI interfaces:
> 		* customizable set of CDNI Logging fields (e.g. include a customizable set of logging information elements in a given log - possibly with a default set)
> 		* customizable set of CDNI Logging events (e.g. include logs for a customizable set of events -eg for delivery but not for redirection)
> 	o Do _not_ aim to support in the first version of the CDNI interfaces:
> 		* a signaling mechanism to control such Logging customization.
> 
> The rationale behind this proposal includes:
> 	* for initial CDNI deployments, it is reasonable to rely on "management plane". In other words, humans in uCDN and dCDN can agree on what events are to be logged by the other CDN and what set of logging fields are to be included, and then humans in uCDN and dCDN can configure their CDNI Logging systems accordingly.
> 	* while a signaling mechanism allowing automation of such customization would be nice (and is a good candidate work item if/when CDNI WG recharters) it is not an absolute-must-have for initial deployment
> 	* defining such a signaling mechanism would require non-negligible time and energy, that may be better spent in the short term on developing the CDNI Logging interface itself that is not progressing as fast as needed
> 
> Additional points:
> 	* there was no convergence among us on which CDNI interface (CDNI Control or CDNI Metadata) should be used for signaling CDNI Logging customization/control, if/when we decide to specify that
> 	* authors of the CDNI Metadata interface felt it is likely that the Metadata interface could be extended later to support CDNI Logging customization/control, if/when we decide to specify it and if we decide to include it in the CDNI Metadata interface. Authors of the CDNI Metadata are requested to keep this topic in the back of their head to facilitate such potential extension
> 	* If the CDNI Control interface was to be used for CDNI Logging customization/control, the necessary mechanism would be quite different from the CDNI Trigger proposal because CDNI Logging customization/control requires persistence of state.
> 
> 
> 
> Proposal 2: 
> ========
> 	o Aim to support in the first version of the CDNI interfaces:
> 		* CDNI Logging in the dCDN-->uCDN direction
> 	o Do _not_ aim to support in the first version of the CDNI interfaces:
> 		* CDNI Logging in the uCDN-->dCDN direction
> 
> The rationale behind this proposal includes:
> 	* there is unanimous agreement that CDNI Logging in the dCDN-->uCDN direction is urgently needed
> 	* we did not convergence on whether CDNI Logging in the uCDN-->dCDN direction is really needed and what are the exact use cases for it
> 	* while a few felt that it would probably be useful to have the ability to pass CDNI Logs in the uCDN-->dCDN direction, it is clearly not an absolute-must-have for initial deployment
> 	* since the CDNI Logging protocol itself (whether built on Syslog, IPFIX, web-services,…) is likely to pass information in one direction, adding logs in the opposite direction can be easily done at a later stage by adding another instance of the same protocol with opposite roles on both ends. 
> 	* defining CDNI Logging in the uCDN-->dCDN direction would require non-negligible time and energy, that may be better spent in the short term on developing CDNI Logging in the dCDN-->uCDN direction that is not progressing as fast as needed
> 
> 
> Francois
> 
> 
> (1) Gilles B, Roy P, Emile S, Kevin M, Rob M, Ray v B, Bhumip K, Iuniana, Rich W, Francois LF & a few others part of the time.
> 
> 
> On 18 Dec 2012, at 19:29, Francois Le Faucheur (flefauch) wrote:
> 
>> Just a friendly reminder about tomorrow's informal discussion (08:00 PST = 11:00 EST = 17:00 CET).
>> Talk to you then.
>> Francois
>> 
>> On 29 Nov 2012, at 11:28, Francois Le Faucheur wrote:
>> 
>>> Folks,
>>> 
>>> Meeting has been rescheduled to 19 Dec. So here are the updated details:
>>> 
>>> Date: Wednesday 19 December 2012
>>> Start: 08:00 PST aka 17:00 CET
>>> Duration: 90 mins
>>> Webex details: see below
>>> 
>>> Please mark this in your agenda if you are interested in attending.
>>> 
>>> Again, note that this is not a formal session nor an IETF Interim Meeting. Just an informal discussion to exchange views on that topic.
>>> 
>>> Francois
>>> 
>>> 
>>> 
>>> Webex details:
>>> 
>>> Topic: CDNI Logging Customization/Control 
>>> Date: Wednesday, December 19, 2012 
>>> Time: 5:00 pm, Europe Time (Paris, GMT+01:00) 
>>> Meeting Number: 207 377 422 
>>> Password: cdni 
>>> 
>>> ------------------------------------------------------- 
>>> To join the meeting online 
>>> ------------------------------------------------------- 
>>> 1. Go to https://cisco.webex.com/ciscosales/j.php?ED=211252322&UID=484318167&PW=NMTM0ZDI5MmM0&RT=MiMyMw%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 appear 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_restrictions.pdf 
>>> 
>>> Access code:207 377 422 
>>> 
>>> 
>>> 
>>> 
>>> CCP:+14085256800x207377422# 
>>> 
>>> 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. Please note that any such recordings may be subject to discovery in the event of litigation. 
>>> 
>>> On 28 Nov 2012, at 16:19, Francois Le Faucheur (flefauch) wrote:
>>> 
>>>> Hi,
>>>> 
>>>> It appeared in Atlanta that we need more discussion to conclude on which CDNI interface (CI or MI) is to be used for customization/control of CDNI Logging.
>>>> 
>>>> To facilitate an informal discussion on that topic, I have setup a Webex session for remote participation:
>>>> Date: Wednesday 12 December 2012
>>>> Start: 08:00 PST aka 17:00 CET
>>>> Duration: 90 mins
>>>> Webex details: see below
>>>> 
>>>> Please mark this in your agenda if you are interested in attending.
>>>> 
>>>> Again, note that this is not a formal session nor an IETF Interim Meeting. Just an informal discussion to exchange views on that topic.
>>>> 
>>>> Cheers
>>>> 
>>>> Francois 
>>>> 
>>>> 
>>>> Topic: CDNI Logging Customization/Control 
>>>> Date: Wednesday, December 12, 2012 
>>>> Time: 5:00 pm, Europe Time (Paris, GMT+01:00) 
>>>> Meeting Number: 207 377 422 
>>>> Password: cdni 
>>>> 
>>>> ------------------------------------------------------- 
>>>> To join the meeting online(Now from mobile devices!) 
>>>> ------------------------------------------------------- 
>>>> 1. Go to https://cisco.webex.com/ciscosales/j.php?ED=211252322&UID=484318167&PW=NMTM0ZDI5MmM0&RT=MiMyMw%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 appear 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_restrictions.pdf 
>>>> 
>>>> Access code:207 377 422 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> CCP:+14085256800x207377422# 
>>>> 
>>>> 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. Please note that any such recordings may be subject to discovery in the event of litigation. 
>>>> _______________________________________________
>>>> CDNi mailing list
>>>> [email-masked]
>>>> https://www.ietf.org/mailman/listinfo/cdni
>>> 
>> 
>> _______________________________________________
>> CDNi mailing list
>> [email-masked]
>> https://www.ietf.org/mailman/listinfo/cdni
> 
> _______________________________________________
> CDNi mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/cdni