Re: [OPSAWG] New Version Notification for draft-lear-opsawg-sbom-access-00.txt

Eliot Lear <lear@cisco.com> Thu, 15 October 2020 15:43 UTC

Return-Path: <lear@cisco.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 033FB3A0895 for <opsawg@ietfa.amsl.com>; Thu, 15 Oct 2020 08:43:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.601
X-Spam-Level:
X-Spam-Status: No, score=-9.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 N93DCopTfU3g for <opsawg@ietfa.amsl.com>; Thu, 15 Oct 2020 08:43:21 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 44F9C3A0880 for <opsawg@ietf.org>; Thu, 15 Oct 2020 08:43:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3182; q=dns/txt; s=iport; t=1602776601; x=1603986201; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=OJZAZ3q3VSe4q11AFcbM6jmG19JbkcBPbSfhdbOAC/w=; b=S9YVJo/7xPosESdbi7/K/RCb5CyN8xCIo7IZZojtyqHU0Y0FTpPMYimJ hlUK9eJInKWhBvnqU0ilm2WHwL7bzNJs7QTPlgTPFdqnl2iksbBvjdcmc 29Gf8ZA4Yqf7S7+sd7wPJZwQr5zBy1UcHqdt84hP7u8wcjk0mPkXPXWcV c=;
X-Files: signature.asc : 488
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DvAADmbIhf/xbLJq1gGwEBAQEBAQEBBQEBARIBAQEDAwEBAYIPgxpVASASLIQ9iQKHciacJgQHAQEBCgMBAS8EAQGESgKCCSY4EwIDAQELAQEFAQEBAgEGBG2FaIVyAQEBAwEjVAIFCwsYKgICVwYTgyYBglwgrAN2gTKFVIR0EIE4gVOKRYE5ggCBEScMEIF9UD6CXASBRYMvM4ItBJAEjBaKRZEZgnSDFoE3liEDH5I7jw+veYNgAgQGBQIVgWsjgVczGggbFWUBgj4+EhkNnGUDPwMwAjYCBgEJAQEDCY5IAQE
X-IronPort-AV: E=Sophos;i="5.77,379,1596499200"; d="asc'?scan'208";a="30382379"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 15 Oct 2020 15:43:17 +0000
Received: from [10.61.208.248] ([10.61.208.248]) by aer-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id 09FFhGgq010210 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 15 Oct 2020 15:43:17 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <7CB100BC-1001-4DAE-A073-D67C2F4EA5D7@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_0CC0E591-9E97-4AB5-822A-CDE5F97FB05E"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Thu, 15 Oct 2020 17:43:15 +0200
In-Reply-To: <352.1602704502@localhost>
Cc: opsawg <opsawg@ietf.org>
To: Michael Richardson <mcr+ietf@sandelman.ca>
References: <160260371149.16976.435024798941804386@ietfa.amsl.com> <5A6BF999-4422-47B7-A96B-4C0ACFF6CDD7@cisco.com> <352.1602704502@localhost>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
X-Outbound-SMTP-Client: 10.61.208.248, [10.61.208.248]
X-Outbound-Node: aer-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/raW9ClTznI6hruQlviknP_dENKo>
Subject: Re: [OPSAWG] New Version Notification for draft-lear-opsawg-sbom-access-00.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Oct 2020 15:43:23 -0000


> On 14 Oct 2020, at 21:41, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
> 
> Eliot Lear <lear=40cisco.com@dmarc.ietf.org> wrote:
>> This is the same draft that was presented some time ago to you.
>> However, the emphasis is changed- MUD is not the sole means by which an
>> SBOM can be discovered.  The context will matter.
> 
> okay.
> 
>> My request is that we discuss this in the WG, and then consider it for
>> adoption, understanding that it has a bit of a road to travel still.
> 
> I'm not sure that I understand why you are using the term "layer" in
> "application-layer management system"?  Or maybe it is "application"
> That section reads poorly, even though I eventually understood it.

Yeah, edits welcome.  Imagine a pool of applications servers that you’re managing with a cloud orchestration system.  That’s the use case.

> 
> I understand that it's an *application management system*, because it is
> managing some application server.   But, I don't understand "layer" here,
> which suggests "layer-7", when really the application management system
> really manages all the layers?
> Maybe people think of HTTP as being a kind of layer-5 or 6, rather than 7.
> (But, really nothing beyond layer 4 has any meaning between OSI terminology
> and reality)
> 
> Anyway, I thought that you were going to use a template for local-uri,
> instead of having the enumeration of scheme?

I got an opinion that either we go with .well-known OR we go with a schema, but not both.  I think this is still an open issue, tho.

> 
> While the set of SBOM formats is far from set in stone,  and I think that
> each will have a MIME type, I want to suggest that this document make it
> clear that HTTP content negotiation should be used to get the format
> one wants and/or that the type returned will be tagged via Content-Type.

Agree.

> 
> Should the MUD file contain a text description of what content-type(s) are
> available?   Avoiding for now, any kind if enumeration, aiming just for
> human consumption?

I guess I would want to explore the use case a bit.

Eliot