[OPSAWG]Orie Steele's No Objection on draft-ietf-opsawg-teas-common-ac-14: (with COMMENT)

Orie Steele via Datatracker <noreply@ietf.org> Fri, 17 January 2025 22:57 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: opsawg@ietf.org
Delivered-To: opsawg@ietfa.amsl.com
Received: from [10.244.8.241] (unknown [104.131.183.230]) by ietfa.amsl.com (Postfix) with ESMTP id 5ABEAC1E56C2; Fri, 17 Jan 2025 14:57:24 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Orie Steele via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.32.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <173715464403.1281508.16647793765225206955@dt-datatracker-57c4c68d9c-p9khg>
Date: Fri, 17 Jan 2025 14:57:24 -0800
Message-ID-Hash: HAKWI3ZFDXLOYRCJ52BMWOCNPRAVLEHX
X-Message-ID-Hash: HAKWI3ZFDXLOYRCJ52BMWOCNPRAVLEHX
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-opsawg.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-opsawg-teas-common-ac@ietf.org, opsawg-chairs@ietf.org, opsawg@ietf.org, rrokui@ciena.com
X-Mailman-Version: 3.3.9rc6
Reply-To: Orie Steele <orie@or13.io>
Subject: [OPSAWG]Orie Steele's No Objection on draft-ietf-opsawg-teas-common-ac-14: (with COMMENT)
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/OCWbn1aSDz-I6UdCazF1XlUCPO8>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Owner: <mailto:opsawg-owner@ietf.org>
List-Post: <mailto:opsawg@ietf.org>
List-Subscribe: <mailto:opsawg-join@ietf.org>
List-Unsubscribe: <mailto:opsawg-leave@ietf.org>

Orie Steele has entered the following ballot position for
draft-ietf-opsawg-teas-common-ac-14: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-opsawg-teas-common-ac/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

# Orie Steele, ART AD, comments for draft-ietf-opsawg-teas-common-ac-14
CC @OR13

* line numbers:
  -
  https://author-tools.ietf.org/api/idnits?url=https://www.ietf.org/archive/id/draft-ietf-opsawg-teas-common-ac-14.txt&submitcheck=True

* comment syntax:
  - https://github.com/mnot/ietf-comments/blob/main/format.md

* "Handling Ballot Positions":
  - https://ietf.org/about/groups/iesg/statements/handling-ballot-positions/

## Comments

### md5

```
573                     +--:(md5)
574                     |  +-- md5-keychain?       key-chain:key-chain-ref
```

I assume there is no other choice?

https://www.rfc-editor.org/rfc/rfc8177.html#section-5

```
Similarly, the MD5 and SHA-1 algorithms have been proven to be
insecure ([Dobb96a], [Dobb96b], and [SHA-SEC-CON]), and usage is NOT
RECOMMENDED.  Usage should be confined to deployments where it is
required for backward compatibility.
```

## Nits

### this identity can _be_ used...

```
310           type in an AC.  For example, this identity can used to indicate
```

### is _used_ to control...

```
321        'l2-tunnel-type':  Uses to control the Layer 2 tunnel selection for
```