Formal IESG Teleconference WebEx and Dial-in Information: 27 October 2022

2022-10-20 Thread IESG Secretary 
All members of the community are welcome to attend formal IESG telechats
as observers. Observers are not invited to participate in the
discussion.

The next formal IESG telechat will be held on Thursday, October 27,  
2022 at 07:00 US/Canada Pacific (14:00 UTC). The meeting is scheduled 
for two hours (07:00-09:00 US/Canada Pacific). Webex and Dial-in information 
is at the bottom of this message.

The agenda for the upcoming telechat can be found at


A calendar of upcoming public telechats can be downloaded or subscribed
to at:
https://calendar.google.com/calendar/ical/ietf.org_egdabaf39ch5v8a13dt39mvee4%40group.calendar.google.com/public/basic.ics


Topic: IESG Formal Telechat
Date: October 27, 2022
Time: 07:00 US/Canada Pacific 
09:00 US/Canada Central
10:00 US/Canada Eastern
14:00 UTC
15:00 United Kingdom
16:00 Germany, France, Belgium, Sweden
17:00 Finland, Kenya
 22:00 Beijing, China
  
---
JOIN WEBEX MEETING
https://ietf.webex.com/ietf/j.php?MTID=m38beb3706c7e5a24dd749a50d7e87dfd
Meeting number: 642 944 708
Meeting password: 1234


JOIN BY PHONE
1-650-479-3208 Call-in toll number (US/Canada)
Access code: 642 944 708

___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

RFC 9305 on Locator/ID Separation Protocol (LISP) Generic Protocol Extension

2022-10-20 Thread rfc-editor 
A new Request for Comments is now available in online RFC libraries.


RFC 9305

Title:  Locator/ID Separation Protocol (LISP)
Generic Protocol Extension 
Author: F. Maino, Ed.,
J. Lemon,
P. Agarwal,
D. Lewis,
M. Smith
Status: Standards Track
Stream: IETF
Date:   October 2022
Mailbox:fma...@cisco.com,
jale...@meus.us,
pun...@acm.org,
darle...@cisco.com,
michs...@cisco.com
Pages:  14
Updates/Obsoletes/SeeAlso:   None

I-D Tag:draft-ietf-lisp-gpe-19.txt

URL:https://www.rfc-editor.org/info/rfc9305

DOI:10.17487/RFC9305

This document describes extensions to the Locator/ID Separation
Protocol (LISP) data plane, via changes to the LISP header, to
support multiprotocol encapsulation and allow the introduction of new
protocol capabilities.

This document is a product of the Locator/ID Separation Protocol Working Group 
of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-edi...@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

RFC 9306 on Vendor-Specific LISP Canonical Address Format (LCAF)

2022-10-20 Thread rfc-editor 
A new Request for Comments is now available in online RFC libraries.


RFC 9306

Title:  Vendor-Specific LISP Canonical Address Format (LCAF) 
Author: A. Rodriguez-Natal,
V. Ermagan,
A. Smirnov,
V. Ashtaputre,
D. Farinacci
Status: Experimental
Stream: IETF
Date:   October 2022
Mailbox:na...@cisco.com,
erma...@gmail.com,
asmir...@cisco.com,
vrush...@cisco.com,
farina...@gmail.com
Pages:  5
Updates:RFC 8060

I-D Tag:draft-ietf-lisp-vendor-lcaf-12.txt

URL:https://www.rfc-editor.org/info/rfc9306

DOI:10.17487/RFC9306

This document describes a new  Locator/ID Separation Protocol (LISP)
Canonical Address Format (LCAF), the Vendor-Specific LCAF. This LCAF
enables organizations to have implementation-specific encodings for
LCAF addresses. This document updates RFC 8060.

This document is a product of the Locator/ID Separation Protocol Working Group 
of the IETF.


EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-edi...@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

RFC 9304 on Locator/ID Separation Protocol (LISP): Shared Extension Message and IANA Registry for Packet Type Allocations

2022-10-20 Thread rfc-editor 
A new Request for Comments is now available in online RFC libraries.


RFC 9304

Title:  Locator/ID Separation Protocol (LISP): Shared 
Extension Message and IANA Registry for 
Packet Type Allocations 
Author: M. Boucadair,
C. Jacquenet
Status: Standards Track
Stream: IETF
Date:   October 2022
Mailbox:mohamed.boucad...@orange.com,
christian.jacque...@orange.com
Pages:  5
Obsoletes:  RFC 8113

I-D Tag:draft-ietf-lisp-rfc8113bis-03.txt

URL:https://www.rfc-editor.org/info/rfc9304

DOI:10.17487/RFC9304

This document specifies a Locator/ID Separation Protocol (LISP)
shared message type for defining future extensions and conducting
experiments without consuming a LISP Packet Type codepoint for each
extension.

This document obsoletes RFC 8113.

This document is a product of the Locator/ID Separation Protocol Working Group 
of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-edi...@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

RFC 9303 on Locator/ID Separation Protocol Security (LISP-SEC)

2022-10-20 Thread rfc-editor 
A new Request for Comments is now available in online RFC libraries.


RFC 9303

Title:  Locator/ID Separation Protocol Security (LISP-SEC) 
Author: F. Maino,
V. Ermagan,
A. Cabellos,
D. Saucez
Status: Standards Track
Stream: IETF
Date:   October 2022
Mailbox:fma...@cisco.com,
erma...@gmail.com,
acabe...@ac.upc.edu,
damien.sau...@inria.fr
Pages:  23
Updates/Obsoletes/SeeAlso:   None

I-D Tag:draft-ietf-lisp-sec-29.txt

URL:https://www.rfc-editor.org/info/rfc9303

DOI:10.17487/RFC9303

This memo specifies Locator/ID Separation Protocol Security
(LISP-SEC), a set of security mechanisms that provides origin
authentication, integrity, and anti-replay protection to the LISP's
Endpoint-ID-to-Routing-Locator (EID-to-RLOC) mapping data conveyed
via the mapping lookup process. LISP-SEC also enables verification of
authorization on EID-Prefix claims in Map-Reply messages.

This document is a product of the Locator/ID Separation Protocol Working Group 
of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-edi...@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

RFC 9302 on Locator/ID Separation Protocol (LISP) Map-Versioning

2022-10-20 Thread rfc-editor 
A new Request for Comments is now available in online RFC libraries.


RFC 9302

Title:  Locator/ID Separation Protocol (LISP) Map-Versioning 
Author: L. Iannone,
D. Saucez,
O. Bonaventure
Status: Standards Track
Stream: IETF
Date:   October 2022
Mailbox:luigi.iann...@huawei.com,
damien.sau...@inria.fr,
olivier.bonavent...@uclouvain.be
Pages:  15
Obsoletes:  RFC 6834

I-D Tag:draft-ietf-lisp-6834bis-14.txt

URL:https://www.rfc-editor.org/info/rfc9302

DOI:10.17487/RFC9302

This document describes the Locator/ID Separation Protocol (LISP)
Map-Versioning mechanism, which provides in-packet information about
Endpoint-ID-to-Routing-Locator (EID-to-RLOC) mappings used to
encapsulate LISP data packets. This approach is based on associating
a version number to EID-to-RLOC mappings and transporting such a
version number in the LISP-specific header of LISP-encapsulated
packets. LISP Map-Versioning is particularly useful to inform
communicating Ingress Tunnel Routers (ITRs) and Egress Tunnel Routers
(ETRs) about modifications of the mappings used to encapsulate
packets.  The mechanism is optional and transparent to
implementations not supporting this feature, since in the
LISP-specific header and in the Map Records, bits used for
Map-Versioning can be safely ignored by ITRs and ETRs that do not
support or do not want to use the mechanism. 

This document obsoletes RFC 6834, which is the initial experimental
specifications of the mechanisms updated by this document.

This document is a product of the Locator/ID Separation Protocol Working Group 
of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-edi...@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

RFC 9301 on Locator/ID Separation Protocol (LISP) Control Plane

2022-10-20 Thread rfc-editor 
A new Request for Comments is now available in online RFC libraries.


RFC 9301

Title:  Locator/ID Separation Protocol (LISP) Control Plane 
Author: D. Farinacci,
F. Maino,
V. Fuller,
A. Cabellos, Ed.
Status: Standards Track
Stream: IETF
Date:   October 2022
Mailbox:farina...@gmail.com,
fma...@cisco.com,
vince.ful...@gmail.com,
acabe...@ac.upc.edu
Pages:  42
Obsoletes:  RFC 6830, RFC 6833

I-D Tag:draft-ietf-lisp-rfc6833bis-31.txt

URL:https://www.rfc-editor.org/info/rfc9301

DOI:10.17487/RFC9301

This document describes the control plane and Mapping Service for the
Locator/ID Separation Protocol (LISP), implemented by two types of
LISP-speaking devices -- the LISP Map-Resolver and LISP Map-Server --
that provide a simplified "front end" for one or more Endpoint IDs
(EIDs) to Routing Locator mapping databases.

By using this control plane service interface and communicating with
Map-Resolvers and Map-Servers, LISP Ingress Tunnel Routers (ITRs) and
Egress Tunnel Routers (ETRs) are not dependent on the details of
mapping database systems; this behavior facilitates modularity with
different database designs.  Since these devices implement the "edge"
of the LISP control plane infrastructure, connecting EID addressable
nodes of a LISP site, the implementation and operational complexity
of the overall cost and effort of deploying LISP is reduced.

This document obsoletes RFCs 6830 and 6833.

This document is a product of the Locator/ID Separation Protocol Working Group 
of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-edi...@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

RFC 9300 on The Locator/ID Separation Protocol (LISP)

2022-10-20 Thread rfc-editor 
A new Request for Comments is now available in online RFC libraries.


RFC 9300

Title:  The Locator/ID Separation Protocol (LISP) 
Author: D. Farinacci,
V. Fuller,
D. Meyer,
D. Lewis,
A. Cabellos, Ed.
Status: Standards Track
Stream: IETF
Date:   October 2022
Mailbox:farina...@gmail.com,
vince.ful...@gmail.com,
d...@1-4-5.net,
darle...@cisco.com,
acabe...@ac.upc.edu
Pages:  33
Obsoletes:  RFC 6830

I-D Tag:draft-ietf-lisp-rfc6830bis-38.txt

URL:https://www.rfc-editor.org/info/rfc9300

DOI:10.17487/RFC9300

This document describes the data plane protocol for the Locator/ID
Separation Protocol (LISP). LISP defines two namespaces: Endpoint
Identifiers (EIDs), which identify end hosts; and Routing Locators
(RLOCs), which identify network attachment points. With this, LISP
effectively separates control from data and allows routers to create
overlay networks. LISP-capable routers exchange encapsulated packets
according to EID-to-RLOC mappings stored in a local Map-Cache.

LISP requires no change to either host protocol stacks or underlay
routers and offers Traffic Engineering (TE), multihoming, and
mobility, among other features.

This document obsoletes RFC 6830.

This document is a product of the Locator/ID Separation Protocol Working Group 
of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-edi...@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

RFC 9299 on An Architectural Introduction to the Locator/ID Separation Protocol (LISP)

2022-10-20 Thread rfc-editor 
A new Request for Comments is now available in online RFC libraries.


RFC 9299

Title:  An Architectural Introduction to the 
Locator/ID Separation Protocol (LISP) 
Author: A. Cabellos,
D. Saucez, Ed.
Status: Informational
Stream: IETF
Date:   October 2022
Mailbox:acabe...@ac.upc.edu,
damien.sau...@inria.fr
Pages:  24
Updates/Obsoletes/SeeAlso:   None

I-D Tag:draft-ietf-lisp-introduction-15.txt

URL:https://www.rfc-editor.org/info/rfc9299

DOI:10.17487/RFC9299

This document describes the architecture of the Locator/ID Separation
Protocol (LISP), making it easier to read the rest of the LISP
specifications and providing a basis for discussion about the details
of the LISP protocols. This document is used for introductory
purposes; more details can be found in the protocol specifications,
RFCs 9300 and 9301.

This document is a product of the Locator/ID Separation Protocol Working Group 
of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-edi...@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

Questionnaires, schedule update, second call for nominations

2022-10-20 Thread NomCom Chair 2022 
The NomCom finished work on the questionnaires. Everyone who accepted a 
nomination should be getting a copy via email. They are also available on-line 
at https://datatracker.ietf.org/nomcom/2022/questionnaires/ Nominations are 
still open, until October 26; I will send out another reminder.

The NomCom updated its schedule. That is available at the home page at 
https://datatracker.ietf.org/nomcom/2022  The following changes were made:
October 20: Questionnaires available for candidates
October 26: Deadline for nominations
November 2: Deadline for acceptance and questionnaire responses
November 2: Call for community feedback

-Rich Salz, IETF NomCom 2022-2023 Chair

___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

Reminder: Call for Papers: IAB workshop on Environmental Impact of Internet Applications and Systems

2022-10-20 Thread IAB Executive Administrative Manager 
IAB workshop on Environmental Impact of Internet Applications and 
Systems

Web page: https://www.iab.org/activities/workshops/e-impact/

Background

Internet communications and applications have both environmental costs 
and benefits. In the positive direction, they can reduce the 
environmental impact of our society, for instance, by allowing virtual 
interaction to replace physical travel. Of course, the Internet can 
equally well act as an enabler for increasing physical goods 
consumption, for instance, through easing commerce.

Beyond the effects associated with its use, Internet applications do not 
come for free either. The Internet runs on systems that require energy 
and raw materials to manufacture and operate. While the environmental 
benefits of the Internet may certainly outweigh this use of resources in 
many cases, it is incumbent on the Internet industry to ensure that this 
use of resources is minimized and optimized. In many cases, this is 
already an economic necessity due to operational costs. And because many 
consumers, businesses, and civil societies care deeply about the 
environmental impact of the services and technologies they use, there is 
also a clear demand for providing Internet services with minimal 
environmental impact.

This is a broad topic, ranging from technical questions to economics, 
business decisions, and policies. Technical, standards, and research 
communities can help ensure that we have a sufficient understanding of 
the environmental impact of the Internet and its applications. They can 
also help to design the right tools to continue to build and improve all 
aspects of the Internet, such as addressing new functional needs, easing 
of operations, improving performance and/or efficiency, or reducing 
environmental impacts in other ways.

Workshop

The IAB is organizing a workshop to discuss the Internet's environmental 
impact, discuss the evolving needs from industry, and to identify areas 
for improvements and future work. While the focus is on technical 
aspects, the scope is broadly on the entire Internet ecosystem, from the 
communications to the devices, applications, data centers, etc.

The main goal of the workshop is to call further attention to the topic 
and to bring together a diverse stakeholder community to discuss these 
issues. The workshop shall also:

  • Discuss the direct environmental impacts of the Internet, including 
but not limited to energy usage by Internet systems themselves, 
energy usage of the relevant end-user devices, resources needed for 
manufacturing the associated devices, or the environmental impacts 
throughout the lifecycle of Internet systems. Discuss the breakdown 
of those impacts across different system components and operations. 
Predict potential future trends for these impacts based on changed 
usage patterns and emerging technologies.
  • Discuss the indirect environmental impacts of the Internet, i.e., 
its effects on society overall, through enabling communications, 
virtual services, or global commerce.
  • Share information about relevant measurement metrics and data, and 
identify the need for additional metric or measurements.
  • Discuss the need for improvements or associated new functionality.
  • Share information about the societal, business, and regulatory 
situation, to help identify areas of opportunity.
  • Identify areas where further technical work would be most impactful.
  • Discuss specific improvement proposals.

We expect that the workshop discussions connect analysis of the issues 
(e.g., scale of energy consumption or carbon footprint) to industry 
needs (e.g., deployment opportunities) and solutions.

Business and societal policy questions are in scope only insofar as they 
inform the workshop participants about the context we are in, but what 
those policies should be is not for the workshop to decide or even 
extensively discuss. The scope excludes also how the technical community 
works and meets, such as the question of in-person or hybrid meetings 
(but note that this workshop is virtual).

Practical details

The workshop is organized as three half-day virtual meetings starting 
with a kick-off on Monday, December 5, 2022. The remaining sessions will 
be scheduled according to participant availability, likely also in the 
same week. A workshop report will be prepared after the meeting, to be 
discussed among the participants and then published as an RFC.

Note: While the workshop results are open, the participants may decide 
at the beginning of the meeting that specific contributions and 
discussions can only be shared anonymously, i.e., without attribution or 
inclusion of other identifying information.

Workshop participation is by invitation. Invitations are extended based 
on program committee reviews of position paper submissions. Position 
papers are typically short (2-4 pages) summaries of the participants' 
thinking of a specifi

Last Call: (Problem Details for HTTP APIs) to Proposed Standard

2022-10-20 Thread The IESG 


The IESG has received a request from the Building Blocks for HTTP APIs WG
(httpapi) to consider the following document: - 'Problem Details for HTTP
APIs'
   as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-c...@ietf.org mailing lists by 2022-11-03. Exceptionally, comments may
be sent to i...@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   This document defines a "problem detail" to carry machine-readable
   details of errors in HTTP response content and/or fields to avoid the
   need to define new error response formats for HTTP APIs.

   This document obsoletes RF7807.

Discussion Venues

   This note is to be removed before publishing as an RFC.

   Source for this draft and an issue tracker can be found at
   https://github.com/ietf-wg-httpapi/rfc7807bis.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-httpapi-rfc7807bis/



No IPR declarations have been submitted directly on this I-D.





___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

Last Call: (Messaging Use Cases and Extensions for STIR) to Proposed Standard

2022-10-20 Thread The IESG 


The IESG has received a request from the Secure Telephone Identity Revisited
WG (stir) to consider the following document: - 'Messaging Use Cases and
Extensions for STIR'
   as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-c...@ietf.org mailing lists by 2022-11-03. Exceptionally, comments may
be sent to i...@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   Secure Telephone Identity Revisited (STIR) provides a means of
   attesting the identity of a telephone caller via a signed token in
   order to prevent impersonation of a calling party number, which is a
   key enabler for illegal robocalling.  Similar impersonation is
   sometimes leveraged by bad actors in the text and multimedia
   messaging space.  This document explores the applicability of STIR's
   Personal Assertion Token (PASSporT) and certificate issuance
   framework to text and multimedia messaging use cases, including
   support both for messages carried as a payload in SIP requests and
   for messages sent in sessions negotiated by SIP.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-stir-messaging/



No IPR declarations have been submitted directly on this I-D.





___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

Last Call: (Identity Header Errors Handling) to Proposed Standard

2022-10-20 Thread The IESG 


The IESG has received a request from the Secure Telephone Identity Revisited
WG (stir) to consider the following document: - 'Identity Header Errors
Handling'
   as Proposed
  Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-c...@ietf.org mailing lists by 2022-11-03. Exceptionally, comments may
be sent to i...@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   This document extends STIR and the Authenticated Identity Management
   in the Session Initiation Protocol (SIP) error handling procedures to
   include the mapping of verification failure reasons to STIR defined
   4xx codes so the failure reason of an Identity header field can be
   conveyed to the upstream authentication service when local policy
   dictates that the call should continue in the presence of a
   verification failure.  This document also defines procedures that
   enable a failure reason to be mapped to a specific Identity header
   for scenarios that use multiple Identity header fields where some may
   have errors and others may not and the handling of those situations
   is defined.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-stir-identity-header-errors-handling/



No IPR declarations have been submitted directly on this I-D.





___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce