[CDNi] Triggers "-14"

"Murray, Rob (Nokia - GB)" <rob.murray@nokia.com> Mon, 16 May 2016 16:02 UTC

From: "Murray, Rob (Nokia - GB)" <rob.murray@nokia.com>
To: "cdni@ietf.org" <cdni@ietf.org>, EXT Alexey Melnikov <aamelnikov@fastmail.fm>
Thread-Topic: Triggers "-14"
Thread-Index: AQHRr4w2V/rMtLbxfEKEzVqgbiRuiw==
Date: Mon, 16 May 2016 16:01:32 +0000
Message-ID: <D1FD00B5-E827-4FF1-873E-DE86FA9CE8A3@alcatel-lucent.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/f.16.0.160506
Content-Type: text/plain; charset="utf-8"
Content-ID: <04EBF280F671884F90F2B7DA9B5EB514@exchange.lucent.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/cdni/3wvn5sAVwpxnghIjTjcqu37DHBk>
Subject: [CDNi] Triggers "-14"
Precedence: list

Hi all,

I've uploaded a "-14" of the triggers draft addressing some of Alexey's comments.


  URL:      https://www.ietf.org/internet-drafts/draft-ietf-cdni-control-triggers-14.txt
  Status:   https://datatracker.ietf.org/doc/draft-ietf-cdni-control-triggers/
  Htmlized: https://tools.ietf.org/html/draft-ietf-cdni-control-triggers-14
  Diff:     https://www.ietf.org/rfcdiff?url2=draft-ietf-cdni-control-triggers-14


The main changes are:

  - Added registries for error codes and trigger types

    Specified what a dCDN should do if it gets a request for a
    trigger it doesn't recognize, new error code "eunsupported".

    Then it made sense to remove the MUST implement the trigger
    types specified in the draft (invalidate/purge/preposition).

    Support for a given trigger type will be something for a
    dCDN to advertise via the FCI interface when that's ready.

    That means a CDN that doesn't want to implement "preposition"
    (for example) can now still be compliant with the interface,
    which seems like a good-thing.

    Error codes are simple, and there for info for the uCDN making
    a request, so I plumped for "Specification Required" for that
    registry. But adding a trigger type seems a lot more involved
    and likely to need wider review, so I've said that should be
    "RFC Required".
	
  - Now the media type for all the JSON messages defined by this
    RFC MUST have a "+json". Examples updated to match.

  - Made it clear that the URLs are http/https URLs.

  - Added normative refs RFC-1930 (for AS numbers), RFC-5226 (IANA).

Any objections/comments, please let me know.

(Alexey - I don't think we've concluded on all your AD review comments, but
I thought it'd be worth to pushing out an update anyway to keep the ball
rolling. Let me know if any further change or discussion is needed. The last
email was https://mailarchive.ietf.org/arch/msg/cdni/UnT_ClDjhu9jrBfw-W6jKoMsbXI )

Cheers,
Rob.

[CDNi] Triggers "-14" Murray, Rob (Nokia - GB)