[dhcwg] RFC 8357 on Generalized UDP Source Port for DHCP Relay

rfc-editor@rfc-editor.org Wed, 07 March 2018 06:46 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4548C127601; Tue, 6 Mar 2018 22:46:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 iEsFeqwiWnND; Tue, 6 Mar 2018 22:46:44 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7963124BE8; Tue, 6 Mar 2018 22:46:44 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 066BDB80F09; Tue, 6 Mar 2018 22:46:28 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, dhcwg@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180307064628.066BDB80F09@rfc-editor.org>
Date: Tue, 06 Mar 2018 22:46:28 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/WjqUfUt2YzQWpI6bewSsIcwK4pY>
Subject: [dhcwg] RFC 8357 on Generalized UDP Source Port for DHCP Relay
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2018 06:46:46 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8357

        Title:      Generalized UDP Source Port 
                    for DHCP Relay 
        Author:     N. Shen, 
                    E. Chen
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2018
        Mailbox:    naiming@cisco.com, 
                    enkechen@cisco.com
        Pages:      10
        Characters: 21266
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dhc-relay-port-10.txt

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

        DOI:        10.17487/RFC8357

This document defines an extension to the DHCP protocols that allows
a relay agent to use any available source port for upstream
communications.  The extension also allows inclusion of a DHCP option
that can be used to statelessly route responses back to the
appropriate source port on downstream communications.


This document is a product of the Dynamic Host Configuration 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-editor@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