Internet Area Working Group (intarea) Internet Drafts

      
 IP Tunnels in the Internet Architecture
 
 draft-ietf-intarea-tunnels-14.txt
 Date: 03/11/2024
 Authors: Joseph Touch, Mark Townsley
 Working Group: Internet Area Working Group (intarea)
 This document discusses the role of IP tunnels in the Internet architecture. An IP tunnel transits IP datagrams as payloads in non- link layer protocols. This document explains the relationship of IP tunnels to existing protocol layers and the challenges in supporting IP tunneling, based on the equivalence of tunnels to links. The implications of this document updates RFC 4459 and its MTU and fragmentation recommendations for IP tunnels.
 Communicating Proxy Configurations in Provisioning Domains
 
 draft-ietf-intarea-proxy-config-02.txt
 Date: 20/10/2024
 Authors: Tommy Pauly, Dragana Damjanovic
 Working Group: Internet Area Working Group (intarea)
 This document defines a mechanism for accessing provisioning domain information associated with a proxy, such as other proxy URIs that support different protocols and a list of DNS zones that are accessible via a proxy. 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/tfpauly/privacy-proxy.
 Extending ICMP for Node Identification
 
 draft-ietf-intarea-extended-icmp-nodeid-00.txt
 Date: 30/09/2024
 Authors: Bill Fenner, Reji Thomas
 Working Group: Internet Area Working Group (intarea)
 RFC5837 describes a mechanism for Extending ICMP for Interface and Next-Hop Identification, which allows providing additional information in an ICMP error that helps identify interfaces participating in the path. This is especially useful in environments where each interface may not have a unique IP address to respond to, e.g., a traceroute. This document introduces a similar ICMP extension for Node Identification. It allows providing a unique IP address and/or a textual name for the node, in the case where each node may not have a unique IP address (e.g., the IPv6 nexthop deployment case described in draft-chroboczek-intarea-v4-via-v6).

data-group-menu-data-url="/group/groupmenu.json">

Internet Area Working Group (intarea)

WG Name Internet Area Working Group
Acronym intarea
Area Internet Area (int)
State Active
Charter charter-ietf-intarea-01 Approved
Document dependencies
Additional resources Issue tracker, Wiki, Zulip stream
Personnel Chairs Juan-Carlos Zúñiga, Wassim Haddad
Area Director Éric Vyncke
Mailing list Address int-area@ietf.org
To subscribe https://www.ietf.org/mailman/listinfo/int-area
Archive https://mailarchive.ietf.org/arch/browse/int-area/
Chat Room address https://zulip.ietf.org/#narrow/stream/intarea

Charter for Working Group

The Internet Area Working Group (INTAREA WG) acts primarily as a forum
for discussing far-ranging topics that affect the entire area. Such
topics include, for instance, address space issues, basic IP layer
functionality, and architectural questions. The group also serves as a
forum to distribute information about ongoing activities in the area,
create a shared understanding of the challenges and goals for the area,
and to enable coordination.

The Internet Area receives occasional proposals for the development and
publication of RFCs that are not in scope of an existing working group
and do not justify the formation of a new working group. The INTAREA WG
has a secondary role to serve as the forum for developing such work
items in the IETF. The working group milestones are updated as needed
to reflect the current work items and their associated milestones.

New work must satisfy the following conditions:

(1) WG consensus on the relevance for the Internet at large.

(2) WG consensus on the suitability and projected quality of the
proposed work item.

(3) A core group of WG participants with sufficient energy and
expertise to advance the work item according to the proposed
schedule.

(4) Commitment from the WG as a whole to provide sufficient
and timely review of the proposed work item.

(5) Agreement by the ADs, who, depending on the scope of the proposed
work item, may decide that an IESG review is needed first.

Milestones

Date Milestone Associated documents
Aug 2010 Submission of tunneling security issues document to the IESG as Info
Aug 2010 Submission of tunneling issues document to the IESG as Info
May 2010 Submission of IPID document to the IESG as PS