port registration (was: Re: [VCARDDAV] Lars DISCUSS on draft-ietf-vcarddav-carddav)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

port registration (was: Re: [VCARDDAV] Lars DISCUSS on draft-ietf-vcarddav-carddav)



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

The revised procedures in draft-ietf-tsvwg-iana-ports might have an
interesting impact on AppsArea technologies, since we have registered a
fair number of ports, DNS SRV records, etc. Has anyone here thought much
about the potential impact?

/psa

- -------- Original Message --------
Subject: Re: [VCARDDAV] Lars DISCUSS on draft-ietf-vcarddav-carddav
Date: Thu, 22 Oct 2009 16:04:47 -0400
From: Cyrus Daboo <cyrus at daboo.name>
To: Simon Perreault <simon.perreault at viagenie.ca>, vcarddav at ietf.org
References: <20091019114100.A27AD3A6862 at core3.amsl.com>
<4AE09897.3030208 at isode.com> <4AE0B2EA.9020105 at viagenie.ca>

Hi Simon,

- --On October 22, 2009 3:30:50 PM -0400 Simon Perreault
<simon.perreault at viagenie.ca> wrote:

>> 1). Register the new service names as aliases for ports 80/443
>> 2). Register 2 new port numbers
>> 3). Don't do any change in this area, wait for
>> draft-ietf-tsvwg-iana-ports to get published.
>
> 3 is the way to go.
>
> Naive suggestion: I think IANA will merge its port-numbers with Stuart
> Cheshire's list once draft-ietf-tsvwg-iana-ports is published. Why not
> add the SRV in that list until then?

SRVs are scattered around all over the place. Stuart's list is one place,
several RFCs also define some. At this point it would only confuse matters
to have it in two places. The authors of iana-ports are fully aware that
they need to go through RFCs and Stuarts data to pre-populate the new
registry.

- --
Cyrus Daboo

_______________________________________________
VCARDDAV mailing list
VCARDDAV at ietf.org
https://www.ietf.org/mailman/listinfo/vcarddav
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkrgvtIACgkQNL8k5A2w/vwzLQCgk3LCGpNodmixsFkbzA/9ya4d
6ywAoOdYCcu225Ax4CkVrUVhRjFkO3+y
=yF7a
-----END PGP SIGNATURE-----

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.