> I notice most names in IETF are still presented in the English order,
> given name first and family name later.
same issue with japanese names. there seems to be a convention of
capitalizing the family name
randy
On 12/07/13 05:21, Randy Bush wrote:
I notice most names in IETF are still presented in the English order,
given name first and family name later.
same issue with japanese names. there seems to be a convention of
capitalizing the family name
randy
Indeed a good practice. Capitalizing the fam
On Wed, Jul 10, 2013 at 5:39 PM, Dave Crocker wrote:
> On 7/10/2013 11:59 AM, Russ Housley wrote:
>
>> The IAB has made a statement on dotless domains. You can find this
>> statement here:
>> http://www.iab.org/documents/**correspondence-reports-**
>> documents/2013-2/iab-**statement-dotless-dom
On 07/12/2013 08:16 AM, Phillip Hallam-Baker wrote:
And before people start bringing up all the reasons I am wrong here,
first consider the fact that for many years it was IETF ideology that
NATs were a terrible thing that had to be killed. A position I suspect
was largely driven by some aggr
On Fri, Jul 12, 2013 at 8:58 AM, Keith Moore wrote:
> On 07/12/2013 08:16 AM, Phillip Hallam-Baker wrote:
>
>>
>> And before people start bringing up all the reasons I am wrong here,
>> first consider the fact that for many years it was IETF ideology that NATs
>> were a terrible thing that had to
On 07/12/2013 09:28 AM, Phillip Hallam-Baker wrote:
On Fri, Jul 12, 2013 at 8:58 AM, Keith Moore
mailto:mo...@network-heretics.com>> wrote:
On 07/12/2013 08:16 AM, Phillip Hallam-Baker wrote:
And before people start bringing up all the reasons I am wrong
here, first consid
To be clear here, I do not think the IETF conference fee to be at all
unreasonable. I have paid it out of my own pocket on occasion.
My concern here is that arguments of the form 'we can't change the
conference model because IETF needs the money' will lead to disaster. The
Internet is changing a l
On Fri, Jul 12, 2013 at 1:14 AM, Hui Deng wrote:
> I really don't know whether IETF should recommend Deng Hui or Hui Deng
That's the question! :-D
I believe the Chinese participants should reach this consensus
themselves and let the IETF know. Similarly for other groups, e.g.
Japanese -- when I
> From: Phillip Hallam-Baker
> for many years it was IETF ideology that NATs were a terrible thing
> that had to be killed. A position I suspect was largely driven by some
> aggressive lobbying by rent-seeking ISPs looking to collect fees on a
> per device basis rather than pe
Keith, read my words, I choose them more carefully than you imagine.
solves their problems at negligible cost TO THEM
What part of that do you disagree with? I don't dispute the fact that NAT
is a suboptimal solution if we look at the system as a whole. But the
reason I deployed NAT in my house w
On Fri, Jul 12, 2013 at 10:10 AM, Noel Chiappa wrote:
>
Anyone who tried to
> monetize per-device would have had competition from people who only charged
> based on their actual costs.
So not deploying NAT would somehow magically cause a second broadband
provider to unroll a fiber optic cable
On Fri, Jul 12, 2013 at 10:22 AM, Paul Wouters wrote:
> On Fri, 12 Jul 2013, Phillip Hallam-Baker wrote:
>
>> And I don't expect things to be different this time round. But in ten
>> years time it will be obvious that
>> domains are going to be dotless and three of the biggest dotless domains
>>
Based on the approval of draft-ietf-trill-fine-labeling, the directory
framework document should mention TRILL Fine Grained Labels.
Thanks,
Donald
=
Donald E. Eastlake 3rd +1-508-333-2270 (cell)
155 Beaver Street, Milford, MA 01757 USA
d3e...@gmail.com
On Thu, Ju
dear chair,
this link
http://nomcom.icann.org/bylaws.htm is not opening !
pls. re-check and advise.
thank you,
Arbogast Fabian,
cell:+255-78-447-8387
> Subject: Second Call for Volunteers to Serve on the ICANN Nominating Committee
> From: iab-ch...@iab.org
> Date: Tue, 9 Jul 2013
And the -05 version includes the text to address that editorial nit - it's
ready for publication as a Proposed Standard RFC. Many thanks to the authors
for productively addressing the review comments.
Thanks,
--David
> -Original Message-
> From: Black, David
> Sent: Monday, July 08, 2013
Cyrus,
Even the notion of "First Name" and "Last Name" is specific to a certain group
of cultures. "Family Name" and "Given Name" don't always go in the same order,
and it is not always the case that people are called by their given name in
informal situations, as you can see in the drafts o
Why are newcomers attending the IETF? There seems to be an assumption
that they're coming to participate across the board, or that they should
be encouraged to do so.
Perhaps that's because it's the model that senior / old-time IETFers
follow - they're involved in many different groups.
Ho
On Fri, 12 Jul 2013, Keith Moore wrote:
On 07/12/2013 09:28 AM, Phillip Hallam-Baker wrote:
On Fri, Jul 12, 2013 at 8:58 AM, Keith Moore
wrote:
On 07/12/2013 08:16 AM, Phillip Hallam-Baker wrote:
And before people start bringing up all the reasons I am
wro
On Fri, 12 Jul 2013, Paul Wouters wrote:
I clearly meant 192.168.1.1 to go to Keith Moore, but the terribly gmail
quoting method confused me in who said what :P
Paul
Date: Fri, 12 Jul 2013 10:12:24
From: Paul Wouters
Cc: Phillip Hallam-Baker ,
IETF Discussion Mailing List
To: Keith Moore
On Fri, 12 Jul 2013, Phillip Hallam-Baker wrote:
Today most people have come to accept my position on NAT, in fact it has become
the mainstream position.
Or perhaps I was not. But I guess it's software written by those three
companies listed below that's "soo good" that makes quoting clear :P
On Fri, 12 Jul 2013, Phillip Hallam-Baker wrote:
I notice you are missing .oracle and .exchange and .mail. Is that
because you can't take any more slaps on the back or because you know
too many companies that have servers in their domain that would get
bypassed by your awesome magic three softwa
http://www.icann.org/en/about/governance/bylaws
On Jul 12, 2013, at 10:02 AM, Fabian Jr wrote:
> dear chair,
>
> this link
> http://nomcom.icann.org/bylaws.htm is not opening !
>
>
> pls. re-check and advise.
>
> thank you,
>
>
>
> Arbogast Fabian,
> cell:+255-78-447-8387
>
>
> > S
>>> domains are going to be dotless and three of the biggest dotless domains
>>> are going to be called .apple and .microsoft and .google and they are going
I've read the applications for .apple, .microsoft, and .google. None
of them propose to use dotless names, only the usual 2LDs. At this
pon
On Fri, Jul 12, 2013 at 11:02 AM, Paul Wouters wrote:
> On Fri, 12 Jul 2013, Phillip Hallam-Baker wrote:
>
> I notice you are missing .oracle and .exchange and .mail. Is that
>> because you can't take any more slaps on the back or because you know
>> too many companies that have servers in their
On Fri, Jul 12, 2013 at 12:23 PM, John Levine wrote:
> >>> domains are going to be dotless and three of the biggest dotless
> domains
> >>> are going to be called .apple and .microsoft and .google and they are
> going
>
> I've read the applications for .apple, .microsoft, and .google. None
> of
On Jul 12, 2013, at 5:03 PM, Scott Brim
wrote:
> On Fri, Jul 12, 2013 at 1:14 AM, Hui Deng wrote:
>> I really don't know whether IETF should recommend Deng Hui or Hui Deng
>
> That's the question! :-D
>
> I believe the Chinese participants should reach this consensus
> themselves and let the
> Do you think they are lying when they say they won't be dotless?
Since http://dotless won't work in any host that has a default domain
configured, which as far as I can tell is most hosts on earth, I
don't think they're lying.
It may be stupid and a license to print money, but that's another st
Hi.
I've been trying to stay out of the broader conversation here,
but it seems to have gone far enough into general issues...
Disclaimer and context: I felt that the DNS was better off with
deep hierarchy since before the work that led to RFC 1591
started. I hadn't changed my mind when the NRC
The IETF Administrative Oversight Committee (IAOC) will hold a session from
1500-1650 in
Potsdam 1 at the Berlin IETF on Sunday July 28, 2013. The purpose is to
provide an
overview of the IAOC to allow the community to better understand what the IAOC
does, how
the finances work, venue selection
Since http://dotless won't work in any host that has a default domain
configured, ...
It's worse than that. If there is a name "dotless" in the default domain,
it'll find that one, otherwise it'll fall back to the TLD.
Point your browser at http://dk/ or http://tm/ and see what happens.
For
On 12/07/2013 14:16, Phillip Hallam-Baker wrote:
> The DNS is going to go dotless. That is inevitable when people are
> paying a quarter million dollars to get a dotless domain from ICANN.
> Trying to control the situation with contractual language assumes that
> ICANN is going to forgo large amou
I kept my maiden name, too. Another Western option, hyphenation, was not for
us. Who wants to be a Spear-Burger? Unless you want a Pepsi and chips with
that. See http://en.wikipedia.org/wiki/Olympia_Cafe
On Jul 10, 2013, at 9:00 PM, Ida wrote:
>
>
> Sent from my iPad
>
> On 2013-07-10, at 8
Hi Bob,
IMO the questions/comments that may be ok to see added to discuss are:
1) Venue selection and operation of the IETF meetings
- Selection of the current venue and was there difficulties until
getting to this meeting session time. From the managing meeting
(providing servic
33 matches
Mail list logo
