Re: [CCAMP] Shepherd writeup for "draft-ietf-ccamp-layer1-types" and "draft-ietf-ccamp-otn-topo-yang"

Hi Dan,

thanks a lot.

+1 on adding URLs, they are often pretty useful and yes, they can be added
when addressing the RTG DIR review.

One quick question on G.sup43. If i correctly remember back in the days we
worked on GMPLS extensions for OTN we excluded it as it was not standard.
Indeed RFC 7963 is informational.

Would this potentially be an issue also here?

Thanks
Daniele

On Mon, Mar 6, 2023 at 6:01 PM <daniel@olddog.co.uk> wrote:

> Ciao, Daniele and I-D Authors.
>
> Please note that I updated the Shepherd Writeups for two (related)
> documents:
>
> draft-ietf-ccamp-layer1-types-15
> draft-ietf-ccamp-otn-topo-yang-16
>
> Although my previous comments are mostly addressed, one issue does remain.
> Both documents use Normative and Informative references to non-IETF
> documents, specifically:
>
> [ANSI_T1.105], [IEEE_754], IEEE_802.3], [ITU-T_G.7044], [ITU-T_G.709],
> [MEF63] and [ITU-T_G.Sup43]
>
> However, the documents are publically available via an Internet search, so
> it might be better for the authors to include URLs in the document
> reference details. Since a Routing Area Directorate member is reviewing
> both documents, the URL issue might be addressed in a new version after
> completing the Directorate review.
>
> BR, Dan.
>
> -----Original Message-----
> From: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>
> Sent: Thursday, November 24, 2022 1:43 PM
> To: daniel@olddog.co.uk; 'CCAMP' <ccamp@ietf.org>
> Subject: RE: [CCAMP] Shepherd writeup for
> "draft-ietf-ccamp-layer1-types-14" and "draft-ietf-ccamp-otn-topo-yang-15"
>
> Hi Dan and Authors,
>
> Thanks a lot for the update.
> Regarding your question if it's not too complex to dig it out I would
> suggest to have a publicly available link in the reference. It might also
> not be the latest and greatest but one updated enough to cover the topic
> being referenced (maybe it's simpler to find).
>
> Thanks
> Daniele
>
> > -----Original Message-----
> > From: CCAMP <ccamp-bounces@ietf.org> On Behalf Of daniel@olddog.co.uk
> > Sent: Thursday, 24 November 2022 11:04
> > To: 'CCAMP' <ccamp@ietf.org>
> > Subject: Re: [CCAMP] Shepherd writeup for
> "draft-ietf-ccamp-layer1-types-14"
> > and "draft-ietf-ccamp-otn-topo-yang-15"
> >
> > Dear Chairs, the authors of "draft-ietf-ccamp-layer1-types-14" and
> > "draft-ietf- ccamp-otn-topo-yang-15",
> >
> > Thanks for submitting the new version addressing the various issues.
> >
> > Scanning the CCAMP list, I saw Tom did raise an important question
> > about access to normative references:
> >
> > draft-ietf-ccamp-layer1-types
> > https://www.ietf.org/archive/id/draft-ietf-ccamp-otn-topo-yang-
> > 16.html#name-
> > normative-references
> >
> > draft-ietf-ccamp-otn-topo-yang
> > https://www.ietf.org/archive/id/draft-ietf-ccamp-layer1-types-15.html#
> > name-n
> > ormative-references
> >
> > The ITU-T documents are relatively easy to access via URL, for example:
> >
> > [G.709] https://www.itu.int/rec/T-REC-G.709
> >
> > As Tom mentioned, the IEEE documents are more problematic:
> >
> > [IEEE_754] https://standards.ieee.org/ieee/754/6210/
> >
> > They are easily accessible with a subscription and may also be found
> > without a subscription, but it requires some digging. I will update
> > the Shepherd Write-up for draft-ietf-ccamp-otn-topo-yang, highlighting
> the issue.
> >
> > Finally, do the Chairs want to see a publically accessible URL
> > provided for the normative references?
> >
> > BR, Dan.
> >
> > _______________________________________________
> > CCAMP mailing list
> > CCAMP@ietf.org
> > https://www.ietf.org/mailman/listinfo/ccamp
>
> _______________________________________________
> CCAMP mailing list
> CCAMP@ietf.org
> https://www.ietf.org/mailman/listinfo/ccamp
>