RFC 9249 on A YANG Data Model for NTP

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


RFC 9249

Title:  A YANG Data Model for NTP 
Author: N. Wu,
D. Dhody, Ed.,
A. Sinha, Ed.,
A. Kumar S N,
Y. Zhao
Status: Standards Track
Stream: IETF
Date:   July 2022
Mailbox:eric...@huawei.com,
dhruv.i...@gmail.com,
ankit.i...@gmail.com,
anil.i...@gmail.com,
yi.z.z...@ericsson.com
Pages:  56
Updates/Obsoletes/SeeAlso:   None

I-D Tag:draft-ietf-ntp-yang-data-model-17.txt

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

DOI:10.17487/RFC9249

This document defines a YANG data model that can be used to configure
and manage Network Time Protocol (NTP) version 4.  It can also be
used to configure and manage version 3.  The data model includes
configuration data and state data.

This document is a product of the Network Time Protocols 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


Document Action: 'Vendor Specific LISP Canonical Address Format (LCAF)' to Experimental RFC (draft-ietf-lisp-vendor-lcaf-11.txt)

2022-07-05 Thread The IESG
The IESG has approved the following document:
- 'Vendor Specific LISP Canonical Address Format (LCAF)'
  (draft-ietf-lisp-vendor-lcaf-11.txt) as Experimental RFC

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

The IESG contact persons are Alvaro Retana, Andrew Alston and John Scudder.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-lisp-vendor-lcaf/





Technical Summary
   
   This document describes a new LISP Canonical Address Format (LCAF),
   the Vendor Specific LCAF.  This LCAF enables organizations to have
   internal encodings for LCAF addresses.

Working Group Summary

   The document was first published in 2017, and was quickly adopted 
   and past WG Last Call in 2018.  The document was parked (like other 
  documents) in order to give priority to the main LISP specifications. 

Document Quality

   No known implementations.  This document builds on the experience 
   gained by rfc8060 (this is the reason for it being Experimental).

Personnel

   Document Shepherd: Luigi Iannone
   Responsible Area Director: Alvaro Retana

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


RFC 9231 on Additional XML Security Uniform Resource Identifiers (URIs)

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


RFC 9231

Title:  Additional XML Security Uniform Resource 
Identifiers (URIs) 
Author: D. Eastlake 3rd
Status: Standards Track
Stream: IETF
Date:   July 2022
Mailbox:d3e...@gmail.com
Pages:  47
Obsoletes:  RFC 6931

I-D Tag:draft-eastlake-rfc6931bis-xmlsec-uris-27.txt

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

DOI:10.17487/RFC9231

This document updates and corrects the IANA "XML Security URIs"
registry that lists URIs intended for use with XML digital
signatures, encryption, canonicalization, and key management.  These
URIs identify algorithms and types of information.  This document
also obsoletes and corrects three errata against RFC 6931.

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


New Non-WG Mailing List: mimi

2022-07-05 Thread IETF Secretariat
A new IETF non-working group email list has been created.

List address: m...@ietf.org
Archive: https://mailarchive.ietf.org/arch/browse/mimi/
To subscribe: https://www.ietf.org/mailman/listinfo/mimi

Purpose:
More Instant Messaging Interoperability (MIMI)

Requirements for interoperable Instant Messaging (IM) systems
have changed dramatically since The Common Profile for Instant Messaging
[RFC3860] was published in 2004. The goal of MIMI is to gather requirements
common to many IM systems, focusing on the most immediate needs first; to
identify and evaluate existing solutions to these specific problems; and to
assemble standards and technology which already largely exist into profiles
and best current practices. Where special expertise in another Working
Group or standards body is required, that work would be delegated to the
specialty group.

This list belong IETF area: ART

For additional information, please contact the list administrators.

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