Hi Ari,
At 00:43 15-06-10, Ari Keränen wrote:
On 06/11/2010 09:51 PM, Ben Campbell wrote:
-- 6.1:[ TBD by IANA; 980 ]
Does this mean IANA has already picked the number? Or is it a
recommended number? (Pattern repeats for other registrations)
It's a recommended number. Most of the IANA
getaddrinfo() works for clients.
It does not work for servers, in particular it does not work for
peer-to-peer services that may be hidden behind layers of NAT44, NAT46
and NAT64. Port forwarding requests have to be a part of the model.
That in turn means that there has to be a security model.
The mistake there being to insist on implementation of the IPv6
specification rather than what is necessary to enable the transition
to IPv6.
You can't build a building without scaffolding. In the middle ages the
design of the scaffold was often as great an engineering feat as the
building (c.f.
Anyone can design a system for use by highly motivated geniuses.
It takes a lot more skill to build something that can be used by
people whose primary motivation is not to make 'your stuff' work.
The issue Ned raises is very typical of what most engineers spend 80%
of their time on - fixing
On 6/15/10 11:04 AM, ned+i...@mauve.mrochek.com wrote:
And since I'm not in the best of moods I'll also answer in kind by
saying us application engineers might also be waiting for someone
with half a clue as to how to design a proper standard API to come
along and do that.
Ned,
Agreed,
78th IETF Meeting
Maastricht, Netherlands
July 25-30, 2010
1. Star Alliance Network Discount
2. Registration Types
3. Visas and Letters of Invitation
4. Accommodations Breakfast Information
5. Sponsorship Opportunities
6. IETF 79 (Beijing) Visa Information
1) Star Alliance Network Discount
The IESG has approved the following document:
- 'Use of SRV Records for Locating Email Submission/Access services '
draft-daboo-srv-email-05.txt as a Proposed Standard
This document has been reviewed in the IETF but is not the product of an
IETF Working Group.
The IESG contact person is
The IESG has received a request from the Geographic Location/Privacy WG
(geopriv) to consider the following document:
- 'Geolocation Policy: A Document Format for Expressing Privacy
Preferences for Location Information '
draft-ietf-geopriv-policy-21.txt as a Proposed Standard
Version -11
The IESG has received a request from an individual submitter to consider
the following document:
- 'Requirements to Extend the Datatracker for WG Chairs and Authors '
draft-juskevicius-datatracker-wgdocstate-reqts-04.txt as an Informational
RFC
The IESG plans to make a decision in the next
