public inbox for newlib-cvs@sourceware.org
help / color / mirror / Atom feed
From: Sebastian Huber <sh@sourceware.org>
To: newlib-cvs@sourceware.org
Subject: [newlib-cygwin] Rename IPPROTO 33 from SEP to DCCP
Date: Wed, 25 Sep 2019 07:03:00 -0000	[thread overview]
Message-ID: <20190925070351.109743.qmail@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=28a44b1ecd44ef86ebe98a177d252b9b10343b52

commit 28a44b1ecd44ef86ebe98a177d252b9b10343b52
Author: thj <thj@FreeBSD.org>
Date:   Thu Aug 8 11:43:09 2019 +0000

    Rename IPPROTO 33 from SEP to DCCP
    
    IPPROTO 33 is DCCP in the IANA Registry:
    https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml
    
    IPPROTO_SEP was added about 20 years ago in r33804. The entries were added
    straight from RFC1700, without regard to whether they were used.
    
    The reference in RFC1700 for SEP is '[JC120] <mystery contact>', this is an
    indication that the protocol number was probably in use in a private network.
    
    As RFC1700 is no longer the authoritative list of internet numbers and that
    IANA assinged 33 to DCCP in RFC4340, change the header to the actual
    authoritative source.
    
    Reviewed by:	Richard Scheffenegger, bz
    Approved by:	bz (mentor)
    MFC after:	1 week
    Differential Revision:	https://reviews.freebsd.org/D21178

Diff:
---
 newlib/libc/sys/rtems/include/netinet/in.h | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/newlib/libc/sys/rtems/include/netinet/in.h b/newlib/libc/sys/rtems/include/netinet/in.h
index 727cc88..1ef4672 100644
--- a/newlib/libc/sys/rtems/include/netinet/in.h
+++ b/newlib/libc/sys/rtems/include/netinet/in.h
@@ -29,7 +29,7 @@
  * SUCH DAMAGE.
  *
  *	@(#)in.h	8.3 (Berkeley) 1/3/94
- * $FreeBSD: head/sys/netinet/in.h 326023 2017-11-20 19:43:44Z pfg $
+ * $FreeBSD: head/sys/netinet/in.h 350749 2019-08-08 11:43:09Z thj $
  */
 
 #ifndef _NETINET_IN_H_
@@ -169,7 +169,7 @@ __END_DECLS
 #define	IPPROTO_BLT		30		/* Bulk Data Transfer */
 #define	IPPROTO_NSP		31		/* Network Services */
 #define	IPPROTO_INP		32		/* Merit Internodal */
-#define	IPPROTO_SEP		33		/* Sequential Exchange */
+#define	IPPROTO_DCCP		33		/* Datagram Congestion Control Protocol */
 #define	IPPROTO_3PC		34		/* Third Party Connect */
 #define	IPPROTO_IDPR		35		/* InterDomain Policy Routing */
 #define	IPPROTO_XTP		36		/* XTP */


                 reply	other threads:[~2019-09-25  7:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190925070351.109743.qmail@sourceware.org \
    --to=sh@sourceware.org \
    --cc=newlib-cvs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).