IETF Logo Mail Archive

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

daniel@olddog.co.uk Thu, 24 November 2022 10:04 UTC

Return-Path: <dk@danielking.net>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD705C14F74F for <ccamp@ietfa.amsl.com>; Thu, 24 Nov 2022 02:04:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.644
X-Spam-Level:
X-Spam-Status: No, score=-1.644 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=danielking-net.20210112.gappssmtp.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h_B0cYSO6i9d for <ccamp@ietfa.amsl.com>; Thu, 24 Nov 2022 02:04:01 -0800 (PST)
Received: from mail-wm1-x332.google.com (mail-wm1-x332.google.com [IPv6:2a00:1450:4864:20::332]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E92B6C14F73E for <ccamp@ietf.org>; Thu, 24 Nov 2022 02:04:01 -0800 (PST)
Received: by mail-wm1-x332.google.com with SMTP id i64-20020a1c3b43000000b003d016c21100so3533437wma.3 for <ccamp@ietf.org>; Thu, 24 Nov 2022 02:04:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=danielking-net.20210112.gappssmtp.com; s=20210112; h=content-language:thread-index:content-transfer-encoding :mime-version:message-id:date:subject:in-reply-to:references:cc:to :from:sender:from:to:cc:subject:date:message-id:reply-to; bh=zFpEZRcA5xmsD83bA3q4dzyjLrX75hZ3xkhDY6bRuoU=; b=Mkbt3kNS9xa9RW45rYJVHCUpTlztYFjl1PeWTBYhM+hOrKrvy7t93gLkD3UnMFQeS0 2hJs7DPmQvCFmLAlmSkDWogZlT93XS6Ap0zw+aGXOiqX1uC22SfC0tDXD8VDzJ44Lomz sdqdZNqI27b5F3iKzVYBUpl/kzjbpO6lL9R9fCXSWfpTfdDQt4VZhOn49z4XC1fcdc3r Aj37j5C39bfaOYrz4Mnxd7T9dMegy0EaVGSjQxkmimMm9d9cKCw0m0smreDqUMWNHR9O 2ACZkReBvTqDMVhFJrLk1BD4kW4STIq4yC9vv1hXCbgoqqkMeD8ifFfYjOGAwelbmreQ wMlg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-language:thread-index:content-transfer-encoding :mime-version:message-id:date:subject:in-reply-to:references:cc:to :from:sender:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=zFpEZRcA5xmsD83bA3q4dzyjLrX75hZ3xkhDY6bRuoU=; b=us71OEKM6gnKlTkbzAhqcBTKY1pPrtG4jkfOt6fPUa2WfZZerJ6EnUol2mTn8MCxVa ArludU9BaiGjarR3/fXZin4qAAksjy9UG3c08kV7r13IkhTkrCXPN1pnnKvS81Pc6Mxi ld0mj+rNQ7kRJio9cLiHlN7eQXtLFfGCsNagn/6w06dpbHevU7CMJANOhkBftUrZIiE0 WpXSvEOLhPHrOTTFcxGLLBEyKziKVqXpYWPfaVV/uvANi+CUNNnXVKRiSlLGhk1At0w2 BeoXfsOYctKBTmnc7NQCPhekpQ6aTyoyxXCyxN4beELHSm3FZZw5MNthcq5Nv3Amqcym b6/Q==
X-Gm-Message-State: ANoB5pkjCVIesWGQ3KppQ1wlXRLDGTDmlPVsQCeLcws9ijAcztHNUGt9 Gdxcd/tfkpqFSlV5eSIVvp/HJCVwBC4h4m2a
X-Google-Smtp-Source: AA0mqf4rnlx2x7OdBKz6RVJqxq3Ge3DIpXtELuDODwmiaVWNCB5AAfK1lJHORlBO1aFL/n5eN/jdYQ==
X-Received: by 2002:a05:600c:4e0b:b0:3cf:e850:4437 with SMTP id b11-20020a05600c4e0b00b003cfe8504437mr12633339wmq.51.1669284238427; Thu, 24 Nov 2022 02:03:58 -0800 (PST)
Received: from CIPHER ([2a00:23c7:105:2801:f901:2986:f5ae:63ce]) by smtp.gmail.com with ESMTPSA id o9-20020a5d4a89000000b00241fde8fe04sm919719wrq.7.2022.11.24.02.03.56 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 24 Nov 2022 02:03:56 -0800 (PST)
Sender: Daniel King <dk@danielking.net>
X-Google-Original-Sender: <dk@danielking.net>
From: daniel@olddog.co.uk
To: 'CCAMP' <ccamp@ietf.org>
References: <06df01d8c6d0$3ba50f80$b2ef2e80$@olddog.co.uk>
In-Reply-To: <06df01d8c6d0$3ba50f80$b2ef2e80$@olddog.co.uk>
Date: Thu, 24 Nov 2022 10:03:56 -0000
Message-ID: <0a8601d8ffec$10e94f40$32bbedc0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: Adj/6aR2t4XBA/p2Sc+oqGC+TLDADw==
Content-Language: en-gb
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/GHQjyTyh5HUm4pyhNSAFTfNVuig>
Subject: Re: [CCAMP] Shepherd writeup for "draft-ietf-ccamp-layer1-types-14" and "draft-ietf-ccamp-otn-topo-yang-15"
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ccamp/>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Nov 2022 10:04:05 -0000

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.

v2.23.0 | Report a Bug | By Email