From nobody Sun Mar 21 11:41:01 2021 Return-Path: X-Original-To: alto@ietfa.amsl.com Delivered-To: alto@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D7543A12DE for ; Sun, 21 Mar 2021 11:40:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.197 X-Spam-Level: X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ykXXWsZsBJqD for ; Sun, 21 Mar 2021 11:40:54 -0700 (PDT) Received: from mail-yb1-xb33.google.com (mail-yb1-xb33.google.com [IPv6:2607:f8b0:4864:20::b33]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5CA093A12DC for ; Sun, 21 Mar 2021 11:40:54 -0700 (PDT) Received: by mail-yb1-xb33.google.com with SMTP id j198so4195841ybj.11 for ; Sun, 21 Mar 2021 11:40:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=VRNZD2iFfQDp+hO2bEryRaDZlkR0KtbgoLSxcz39dR0=; b=FzkRjqs+i89edNYkSRlE8Pwm0aEeC4NQRco3xU3gj5lRHR2yXYcECCCc4mSKKRHKPH jLGycAtpSNFfLg8A0iM+eFsYjRMaDYocO9w61uTkTn+EiJ8U+nqFymWpcOja+jm1q4pQ sKhd21vj0wsG6Vb8RanUX2dsyiBqDrxjlk78sPk4kVXmdeSKpBgvC0sW9G3xGJd0wl5l B0qDne7F5YWk9Xj/qrOOPrgq2XidqejpAhyqd4vyggpXaFH42UvSZ0PB+YY0DPNWkwRo Im2oaorpE8s8A/3OlUse0kd8yTz4CeOp4WKJjy/BVtHNdQyrPKQl2a89MUQeeYq7WRZm XEZQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=VRNZD2iFfQDp+hO2bEryRaDZlkR0KtbgoLSxcz39dR0=; b=TizKqJqP8cD8vPYF5fFsDy2QswIxzlQpWOf9Js+IOnFysqhj1AxOQA8weu3PjpLXgu dZtsRDEBMTLTHpiGiokYDVMgVfIr6F25pTSOOf/VkbYul7n3uUUZJ4wQbQ/6SVAGWLbg ohWvQh6Ld1dQs8LuwFycHryAIg3GIh7F8m7HIRTzMSCWw6Z6rY0m19UssT0oG8fwGArO DSP9vZpstdIeNXgPO1mFIsaPGWrGMU6SlN+uWd4pGyejOkGWQmLegxUVHL+8qw+8cCUo y4f6E7pYYW8kHbDgepPCKBXbbs9PIdwpADkqnc6miWXrbHGSlD7PXAQlT4Y8h9w+Yb2A GzGQ== X-Gm-Message-State: AOAM530Okd321L1vTOYhJxMWM2oeQF8WbFbupf55HLrQA2rynjLQjgCz xleuZrWBNvclhmyjpwAX7YZo5hBBQMfYCd1vS8T+AVaH+IC0xg== X-Google-Smtp-Source: ABdhPJzrr/d7QrCJSqftmR1Rk6vEPZ0spdQMWgjskw+Z0aqv2nJcXnHcbpxAuUUEevphjw+FgbhP3efl7zfUaRHe19Q= X-Received: by 2002:a05:6902:708:: with SMTP id k8mr12013396ybt.234.1616352051592; Sun, 21 Mar 2021 11:40:51 -0700 (PDT) MIME-Version: 1.0 From: Vijay Gurbani Date: Sun, 21 Mar 2021 13:40:15 -0500 Message-ID: To: IETF ALTO Content-Type: multipart/alternative; boundary="000000000000de022f05be104902" Archived-At: Subject: [alto] Shepherd write up for cdni-request-routing-alto X-BeenThere: alto@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Mar 2021 18:41:00 -0000 --000000000000de022f05be104902 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable All: The shepherd writeup for CDNI is below. Jan and I will be moving the CNDI draft, path-vector, and unified-props as a cluster. Please let me know if you have any questions on the shepherd writeup. Thanks. 1. Summary Vijay K. Gurbani is the document shepherd for draft-ietf-alto-cdni-request-routing-alto. Martin Duke is the responsible Area Director. RFC 8008 defines the semantics for the CDNI Footprint & Capabilities Advertisement Interface (FCI). This document specifies a concrete protocol for the CDNI FCI using the ALTO protocol. A new ALTO service called the "CDNI Advertisement Service" which conveys JSON objects of media type "application/alto-cdni+json" is defined. This service can convey CDNI FCI Base Advertisement Objects as defined in RFC8008 to ALTO clients via the ALTO protocol. This document is targeted as a Standards Track document (Proposed Standard). This designation is appropriate as the document contains normative behaviour and message formats that should be adhered to by the communicating entities in order to realize the extension. 2. Review and Consensus The =E2=80=9CALTO Service for CDNI FCI=E2=80=9D had been added as a new ALT= O WG milestone in 2017, following an agreement between the CDNI WG and the ALTO WG to finalise the ALTO service for conveying (i.e. transporting) CDNI FCI objects in the ALTO WG. draft-ietf-alto-cdni-request-routing-alto has a long history and had been iterated and presented multiple times in the CDNI WG prior to 2017 (see draft-seedorf-cdni-request-routing-alto). The document is well-known in the ALTO working group and has been presented many times. The approach is agreed upon and no objections have been raised during the WGLC on draft-ietf-alto-cdni-request-routing-alto-09 in February 2020. All comments from the individual reviews during the WGLC have since been addressed and the document has been polished further multiple times since the WGLC (now in draft-ietf-alto-cdni-request-routing-alto-13). In summary, there is clear consensus for draft-ietf-alto-cdni-request-routing-alto in the ALTO WG, and it provides a very useful extension needed also by the CDNI WG to convey CDNI FCI objects defined in RFC8008. A WGLC has successfully been passed, and extensive reviews were provided by various members of the WG and have all been addressed. 3. Intellectual Property The shepherd confirms that each author has stated to him that to the best of his/her (i.e. the author=E2=80=99s) knowledge, all IPR related to this d= ocument has been disclosed. 4. Other Points Note any downward references (see RFC 3967) and whether they appear in the DOWNREF Registry ( http://trac.tools.ietf.org/group/iesg/trac/wiki/DownrefRegistry), as these need to be announced during Last Call. All normative references are ok (with respect to RFC 3967) as they are all towards documents with standards-level =E2=80=9CProposed Standards=E2=80=9D= , =E2=80=9CInternet Standard=E2=80=9D, or =E2=80=9CBCP=E2=80=9D. --000000000000de022f05be104902 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
All: The shepherd writeup for CDNI is below.=C2=A0 Ja= n and I will be moving the CNDI draft, path-vector, and unified-props as a = cluster.=C2=A0 Please let me know if you have any questions on the shepherd= writeup.=C2=A0 Thanks.

1. Summary

Vijay K.= Gurbani is the document shepherd for draft-ietf-alto-cdni-request-routing-= alto. Martin Duke is the responsible Area Director.

RFC 8008 defines= the semantics for the CDNI Footprint & Capabilities Advertisement Inte= rface (FCI). This document specifies a concrete protocol for the CDNI FCI u= sing the ALTO protocol. A new ALTO service called the "CDNI Advertisem= ent Service" which conveys JSON objects of media type "applicatio= n/alto-cdni+json" is defined. This service can convey CDNI FCI Base Ad= vertisement Objects as defined in RFC8008 to ALTO clients via the ALTO prot= ocol.

This document is targeted as a Standards Track document (Prop= osed Standard). This designation is appropriate as the document contains no= rmative behaviour and message formats that should be adhered to by the comm= unicating entities in order to realize the extension.

2. Review and = Consensus
The =E2=80=9CALTO Service for CDNI FCI=E2=80=9D had been added= as a new ALTO WG milestone in 2017, following an agreement between the CDN= I WG and the ALTO WG to finalise the ALTO service for conveying (i.e. trans= porting) CDNI FCI objects in the ALTO WG. draft-ietf-alto-cdni-request-rout= ing-alto has a long history and had been iterated and presented multiple ti= mes in the CDNI WG prior to 2017 (see draft-seedorf-cdni-request-routing-al= to).

The document is well-known in the ALTO working group and has b= een presented many times. The approach is agreed upon and no objections hav= e been raised during the WGLC on draft-ietf-alto-cdni-request-routing-alto-= 09 in February 2020. All comments from the individual reviews during the WG= LC have since been addressed and the document has been polished further mul= tiple times since the WGLC (now in draft-ietf-alto-cdni-request-routing-alt= o-13).

In summary, there is clear consensus for draft-ietf-alto-cdni= -request-routing-alto in the ALTO WG, and it provides a very useful extensi= on needed also by the CDNI WG to convey CDNI FCI objects defined in RFC8008= . A WGLC has successfully been passed, and extensive reviews were provided = by various members of the WG and have all been addressed.

3. Intelle= ctual Property
The shepherd confirms that each author has stated to him = that to the best of his/her (i.e. the author=E2=80=99s) knowledge, all IPR = related to this document has been disclosed.

4. Other Points
Note= any downward references (see RFC 3967) and whether they appear in the DOWN= REF Registry (http://trac.tools.ietf.org/group/iesg/trac/wiki/DownrefRegis= try), as these need to be announced during Last Call.

All normat= ive references are ok (with respect to RFC 3967) as they are all towards do= cuments with standards-level =E2=80=9CProposed Standards=E2=80=9D, =E2=80= =9CInternet Standard=E2=80=9D, or =E2=80=9CBCP=E2=80=9D.
--000000000000de022f05be104902--