All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@redhat.com>
To: dccp@vger.kernel.org
Subject: Re: [RFC] [DCCP]: Deprecate SOCK_DCCP in favour of SOCK_DGRAM
Date: Wed, 14 May 2008 14:06:19 +0000	[thread overview]
Message-ID: <482AF1DB.1060608@redhat.com> (raw)
In-Reply-To: <20080513072853.GB4514@gerrit.erg.abdn.ac.uk>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Gerrit Renker wrote:
> RFC 3493 says that 0 for socktype/protocol means that caller will accept
> any socket type / protocol, so presumably this does include DCCP and UDP-Lite.

I know what the RFC says.  But there are a gazillion of protocols out
there and I won't create a record for all of them in case socktype and
protocol are zero.  That's just overkill in 99.9% of all cases.

I assumption is that UDPlite is just too specialized to be useful to a
wide array of people.  Yes, it case be supported if explicitly requested
but should be returned if 0/0 is passed in.

What I'm asking is whether this is a fair assumption and what the story
of DCCP is.

- --
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFIKvHb2ijCOnn/RHQRAlz5AKCvOSOm7PR7ljfyZ9krq0TtzZUTbgCdFLLj
F1fvWvR+VvXUSE5x+VtgsqQ=3Lft
-----END PGP SIGNATURE-----

WARNING: multiple messages have this Message-ID (diff)
From: Ulrich Drepper <drepper@redhat.com>
To: Gerrit Renker <gerrit@erg.abdn.ac.uk>,
	Ulrich Drepper <drepper@redhat.com>,
	R?mi Denis-Courmont <rdenis@simphalempin.com>,
	Arnaldo Carvalho de Melo <acme@redhat.com>, David Stevens <
Subject: Re: [RFC] [DCCP]: Deprecate SOCK_DCCP in favour of SOCK_DGRAM
Date: Wed, 14 May 2008 07:06:19 -0700	[thread overview]
Message-ID: <482AF1DB.1060608@redhat.com> (raw)
In-Reply-To: <20080514080942.GB4462@gerrit.erg.abdn.ac.uk>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Gerrit Renker wrote:
> RFC 3493 says that 0 for socktype/protocol means that caller will accept
> any socket type / protocol, so presumably this does include DCCP and UDP-Lite.

I know what the RFC says.  But there are a gazillion of protocols out
there and I won't create a record for all of them in case socktype and
protocol are zero.  That's just overkill in 99.9% of all cases.

I assumption is that UDPlite is just too specialized to be useful to a
wide array of people.  Yes, it case be supported if explicitly requested
but should be returned if 0/0 is passed in.

What I'm asking is whether this is a fair assumption and what the story
of DCCP is.

- --
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFIKvHb2ijCOnn/RHQRAlz5AKCvOSOm7PR7ljfyZ9krq0TtzZUTbgCdFLLj
F1fvWvR+VvXUSE5x+VtgsqQ=
=3Lft
-----END PGP SIGNATURE-----

  parent reply	other threads:[~2008-05-14 14:06 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-13  7:28 [RFC] [DCCP]: Deprecate SOCK_DCCP in favour of SOCK_DGRAM Gerrit Renker
2008-05-13  7:28 ` Gerrit Renker
2008-05-13  7:39 ` David Miller
2008-05-13  7:39   ` David Miller
2008-05-13  9:37 ` Gerrit Renker
2008-05-13  9:37   ` Gerrit Renker
2008-05-13 13:46 ` Gerrit Renker
2008-05-13 13:46   ` Gerrit Renker
2008-05-13 15:50 ` David Stevens
2008-05-13 15:50   ` David Stevens
2008-05-13 16:23 ` Arnaldo Carvalho de Melo
2008-05-13 16:23   ` Arnaldo Carvalho de Melo
2008-05-13 16:59 ` David Stevens
2008-05-13 16:59   ` David Stevens
2008-05-13 17:03 ` Gerrit Renker
2008-05-13 17:03   ` Gerrit Renker
2008-05-13 17:06 ` Rémi Denis-Courmont
2008-05-13 17:06   ` Rémi Denis-Courmont
2008-05-13 17:33 ` Arnaldo Carvalho de Melo
2008-05-13 17:33   ` Arnaldo Carvalho de Melo
2008-05-13 17:34 ` Arnaldo Carvalho de Melo
2008-05-13 17:34   ` Arnaldo Carvalho de Melo
2008-05-13 17:37 ` Rémi Denis-Courmont
2008-05-13 17:37   ` Rémi Denis-Courmont
2008-05-13 17:50 ` Arnaldo Carvalho de Melo
2008-05-13 17:50   ` Arnaldo Carvalho de Melo
2008-05-13 17:53 ` Arnaldo Carvalho de Melo
2008-05-13 17:53   ` Arnaldo Carvalho de Melo
2008-05-13 19:14 ` Ulrich Drepper
2008-05-13 19:14   ` Ulrich Drepper
2008-05-13 22:34 ` David Miller
2008-05-13 22:34   ` David Miller
2008-05-14  8:09 ` Gerrit Renker
2008-05-14  8:09   ` Gerrit Renker
2008-05-14 14:06 ` Ulrich Drepper [this message]
2008-05-14 14:06   ` Ulrich Drepper
2008-05-14 14:45 ` Gerrit Renker
2008-05-14 14:45   ` Gerrit Renker
2008-05-14 16:06 ` Ulrich Drepper
2008-05-14 16:06   ` Ulrich Drepper
2008-05-14 17:22 ` Gerrit Renker
2008-05-14 17:22   ` Gerrit Renker
2008-05-14 17:39 ` Sridhar Samudrala
2008-05-14 17:39   ` Sridhar Samudrala
2008-05-14 17:43 ` Ulrich Drepper
2008-05-14 17:43   ` Ulrich Drepper
2008-05-14 17:47 ` Rémi Denis-Courmont
2008-05-14 17:47   ` Rémi Denis-Courmont
2008-05-14 17:49 ` Rémi Denis-Courmont
2008-05-14 17:49   ` Rémi Denis-Courmont
2008-05-14 17:57 ` Ulrich Drepper
2008-05-14 17:57   ` Ulrich Drepper
2008-05-14 18:00 ` Gerrit Renker
2008-05-14 18:00   ` Gerrit Renker
2008-05-14 18:06 ` Ulrich Drepper
2008-05-14 18:06   ` Ulrich Drepper
2008-05-14 18:07 ` Ulrich Drepper
2008-05-14 18:07   ` Ulrich Drepper
  -- strict thread matches above, loose matches on Subject: below --
2008-05-13 12:53 [RFC] [DCCP]: Deprecate SOCK_DCCP in favour of SO Remi Denis-Courmont
2008-05-13 12:53 ` [RFC] [DCCP]: Deprecate SOCK_DCCP in favour of SOCK_DGRAM Remi Denis-Courmont

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=482AF1DB.1060608@redhat.com \
    --to=drepper@redhat.com \
    --cc=dccp@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.