Re: [CDNi] Update of draft-ietf-cdni-redirection

Thanks Kevin.

Ray, can you reflect that ?

On 8 Oct 2015, at 05:09, Kevin Ma J <kevin.j.ma@ericsson.com<mailto:kevin.j.ma@ericsson.com>> wrote:

Hi Francois/Ray,

  For each of the payload type parameters, the spec is supposed to define a purpose, interface, and encoding.  Just to be totally explicit, I've been adding small blurbs for each, e.g., subsection under 6.1:

        <section title="CDNI RI Redirection Request Payload Type">
          <t>Purpose: The purpose of this payload type is to distinguish RI request messages.</t>
          <t>Interface: RI</t>
          <t>Encoding: see <xref target="anchors for Sections 4.4.1 and 4.5.1"/></t>
        </section>
        <section title="CDNI RI Redirection Response Payload Type">
          <t>Purpose: The purpose of this payload type is to distinguish RI response messages.</t>
          <t>Interface: RI</t>
          <t>Encoding: see <xref target="anchors for Sections 4.4.2 and 4.5.2"/></t>
        </section>

  Might also want to add a note to the RFC Editor in section 6.1 to change RFCthis to the published RFC number.

thanx.

--  Kevin J. Ma

From: Francois Le Faucheur (flefauch) [mailto:flefauch@cisco.com]
Sent: Wednesday, October 07, 2015 8:04 AM
To: Peterson, Jon <jon.peterson@neustar.biz<mailto:jon.peterson@neustar.biz>> (jon.peterson@neustar.biz<mailto:jon.peterson@neustar.biz>); Kevin Ma J
Cc: cdni@ietf.org<mailto:cdni@ietf.org>; Brandenburg, R. (Ray) van
Subject: Fwd: [CDNi] Update of draft-ietf-cdni-redirection

Jon,

Can you confirm this new rev addresses your comment appropriately?
I believe the text that was added for that purpose is:
“
3.1.  Redirection of encrypted traffic

     The Redirection Interface defined in this document might be used to

     redirect a request where the User Agent will subsequently attempt to

     establish a TLS session with the Redirection Target.  In such a case,

     any surrogate or request router to which the User Agent is redirected

     needs to be able to successfully complete the TLS handshake and to

     perform encryption of the TLS channel.  Mechanisms to distribute the

     required information and/or configuration, such as private keys, to

     surrogates and request routers in dCDNs are outside the scope of this

     document.
“

Kevin,

Can you confirm that this new rev is fully in line with cdmi-media-type?

Once we have confirmation for these two points we can push the document to IESG review.

Thanks

Begin forwarded message:

From: "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl<mailto:ray.vanbrandenburg@tno.nl>>
Subject: [CDNi] Update of draft-ietf-cdni-redirection
Date: 7 October 2015 10:55:58 CEST
To: "cdni@ietf.org<mailto:cdni@ietf.org>" <cdni@ietf.org<mailto:cdni@ietf.org>>

Hi all,

We've updated draft-ietf-cdni-redirection. This update addresses all open issues, including:

- Updated MIME types to be in line with draft-ietf-cdni-media-types
- Updated security section to be in line with other CDNI docs
- Included short discussion on redirection and TLS

Ray

On 07/10/15 10:52, "CDNi on behalf of internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>" <cdni-bounces@ietf.org<mailto:cdni-bounces@ietf.org> on behalf of internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>> wrote:

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           : Request Routing Redirection Interface for CDN Interconnection
      Authors         : Ben Niven-Jenkins
                        Ray van Brandenburg
Filename        : draft-ietf-cdni-redirection-12.txt
Pages           : 30
Date            : 2015-10-07

Abstract:
 The Request Routing Interface comprises of (1) the asynchronous
 advertisement of footprint and capabilities by a downstream Content
 Delivery Network (CDN) that allows an upstream CDN to decide whether
 to redirect particular user requests to that downstream CDN; and (2)
 the synchronous operation of an upstream CDN requesting whether a
 downstream CDN is prepared to accept a user request and of a
 downstream CDN responding with how to actually redirect the user
 request.  This document describes an interface for the latter part,
 i.e. the CDNI Request Routing Redirection interface.

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

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-cdni-redirection-12

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-cdni-redirection-12

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org<http://tools.ietf.org>.

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
This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. TNO accepts no liability for the content of this e-mail, for the manner in which you use it and for damage of any kind resulting from the risks inherent to the electronic transmission of messages.
_______________________________________________
CDNi mailing list
CDNi@ietf.org<mailto:CDNi@ietf.org>
https://www.ietf.org/mailman/listinfo/cdni