Internet Drafts - IDs for Mar/2023

Index - Month Index of IDs

All IDs - sorted by date)

27/03/2023

	Carrying Binding Label/Segment Identifier (SID) in PCE-based Networks.
	draft-ietf-pce-binding-label-sid-16.txt   Date: 27/03/2023   Authors: Siva Sivabalan, Clarence Filsfils, Jeff Tantsura, Stefano Previdi, Cheng Li   Working Group: Path Computation Element (pce)	In order to provide greater scalability, network confidentiality, and service independence, Segment Routing (SR) utilizes a Binding Segment Identifier (SID) (called BSID) as described in RFC 8402. It is possible to associate a BSID to an RSVP-TE-signaled Traffic Engineering Label Switched Path or an SR Traffic Engineering path. The BSID can be used by an upstream node for steering traffic into the appropriate TE path to enforce SR policies. This document specifies the concept of binding value, which can be either an MPLS label or Segment Identifier. It further specifies an extension to Path Computation Element (PCE) communication Protocol(PCEP) for reporting the binding value by a Path Computation Client (PCC) to the PCE to support PCE-based Traffic Engineering policies.
	HTTP Transport for Trusted Execution Environment Provisioning: Agent Initiated Communication
	draft-ietf-teep-otrp-over-http-15.txt   Date: 27/03/2023   Authors: Dave Thaler   Working Group: Trusted Execution Environment Provisioning (teep)	The Trusted Execution Environment Provisioning (TEEP) Protocol is used to manage code and configuration data in a Trusted Execution Environment (TEE). This document specifies the HTTP transport for TEEP communication where a Trusted Application Manager (TAM) service is used to manage code and data in TEEs on devices that can initiate communication to the TAM.

06/03/2023

	Key Management for OSCORE Groups in ACE
	draft-ietf-ace-key-groupcomm-oscore-16.txt   Date: 06/03/2023   Authors: Marco Tiloca, Jiye Park, Francesca Palombini   Working Group: Authentication and Authorization for Constrained Environments (ace)	This document defines an application profile of the ACE framework for Authentication and Authorization, to request and provision keying material in group communication scenarios that are based on CoAP and are secured with Group Object Security for Constrained RESTful Environments (Group OSCORE). This application profile delegates the authentication and authorization of Clients, that join an OSCORE group through a Resource Server acting as Group Manager for that group. This application profile leverages protocol-specific transport profiles of ACE to achieve communication security, server authentication and proof-of-possession for a key owned by the Client and bound to an OAuth 2.0 Access Token.

---