Ralph Droms | 1 Apr 14:15 2006
Picon

Announcement of IAB member selection


I am pleased to announce that the 2005-2006 NomCom selection and
confirmation process to fill the IAB seat vacated by Pekka Nikander's
resignation is complete.  At this time, on behalf of the NomCom, the
new member of the IAB is:

Bert, Bert <at> secret-wg.org

Bert will complete the remainder of Pekka's term.  The Nomcom
considered Bert's extensive travel and acquaintances with leaders and
personalities around the world.  Although there was question about
Bert's technical accomplishments, his other experience will materially
help the IAB with its representational duties.  The NomCom was also
concerned about Bert's willingness to contribute to IAB activities as
Bert is usually a silent participant in public events.  However, we
note the eloquence and clarity of reasoning Bert demonstrated on video
at IETF 65 in his congratulation to the IETF on its 20th anniversary.

A further consideration is whether Bert would be able to serve a full
term, as it has been rumored he is a candidate to replace Vint Cerf as
chair of ICANN when Vint's term expires.  His photograph count is
approaching Vint's and he has accumulated a similar number of frequent
flyer miles.  Bert was not able to commit, but indicated he has not
yet been offered the ICANN role.

The NomCom joins the rest of the IETF community in thanking Bert for
volunteering his valuable time and extraordinary skills to the IAB,
the IETF comunity and the Internet.

- Ralph Droms (chair), for the 2005-2006 IETF Nominating Committee
(Continue reading)

Thomas Narten | 1 Apr 23:52 2006
Picon

Weekly posting summary for ietf <at> ietf.org

Total of 355 messages in the last 7 days through midnight, Thursday
March 30, EST.

    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  9.58% |   34 |  8.54% |   185628 | moore <at> cs.utk.edu
  5.35% |   19 | 12.43% |   270074 | pbaker <at> verisign.com
  5.92% |   21 |  6.07% |   132036 | brc <at> zurich.ibm.com
  5.92% |   21 |  5.25% |   114207 | anthony <at> atkielski.com
  4.79% |   17 |  5.14% |   111808 | jordi.palet <at> consulintel.es
  3.10% |   11 |  3.50% |    76129 | iljitsch <at> muada.com
  3.38% |   12 |  2.47% |    53695 | jnc <at> mercury.lcs.mit.edu
  3.10% |   11 |  2.51% |    54569 | tjc <at> ecs.soton.ac.uk
  2.82% |   10 |  2.66% |    57924 | ietf <at> andybierman.com
  2.82% |   10 |  2.51% |    54557 | tme <at> multicasttech.com
  2.54% |    9 |  2.47% |    53767 | john-ietf <at> jck.com
  2.25% |    8 |  2.54% |    55309 | sleibrand <at> internap.com
  2.25% |    8 |  2.22% |    48257 | dave <at> cridland.net
  2.25% |    8 |  2.01% |    43632 | tex <at> off.org
  2.25% |    8 |  1.86% |    40389 | spencer <at> mcsr-labs.org
  2.25% |    8 |  1.72% |    37479 | dhc2 <at> dcrocker.net
  1.97% |    7 |  1.86% |    40327 | michel <at> arneill-py.sacramento.ca.us
  1.97% |    7 |  1.85% |    40124 | jefsey <at> jefsey.com
  1.41% |    5 |  1.28% |    27842 | bmanning <at> vacation.karoshi.com
  1.41% |    5 |  1.26% |    27442 | sbrim <at> cisco.com
  1.41% |    5 |  1.21% |    26349 | joelja <at> darkwing.uoregon.edu
  1.13% |    4 |  1.46% |    31838 | stephen <at> sprunk.org
  1.13% |    4 |  1.00% |    21659 | hgs <at> cs.columbia.edu
  1.13% |    4 |  0.89% |    19378 | rpelletier <at> isoc.org
  0.85% |    3 |  0.84% |    18280 | eric.gray <at> marconi.com
(Continue reading)

Henrik Levkowetz | 2 Apr 02:34 2006

Re: Announcement of IAB member selection


I applaud the NomCom in this very appropriate choice -- at this particular
time, I don't think there is any better choice they could possibly have
made for the vacant IAB seat.  Bert has impressed me with his ability to
always perceive where he is most needed, and appear there as if by magic
to assist in whatever needs to be done.  I remember a thorny throughput
issue we ran across some years ago at Casa de Bandini, when Bert came
through as a trouper and helped us make headway with the problem [1].  With
that taken care of, he also showed us his famous ability to make friends
with the ladies [2].

We couldn't wish for a more well-rounded man of the world to step up to
the plate and shoulder his responsibilities today.

	Henrik

[1] http://tinyurl.com/jfsxm
[2] http://tinyurl.com/zccdt

on 2006-04-01 04:15 Ralph Droms said the following:
> 
> I am pleased to announce that the 2005-2006 NomCom selection and
> confirmation process to fill the IAB seat vacated by Pekka Nikander's
> resignation is complete.  At this time, on behalf of the NomCom, the
> new member of the IAB is:
> 
> Bert, Bert <at> secret-wg.org
> 
> Bert will complete the remainder of Pekka's term.  The Nomcom
> considered Bert's extensive travel and acquaintances with leaders and
(Continue reading)

Michel Py | 3 Apr 03:07 2006
Picon
Picon

RE: Stupid NAT tricks and how to stop them.

> Iljitsch van Beijnum wrote:
> you can make it do IPv6 NAT. Simple client-server protocols
> such as HTTP worked without incident as expected. However,
> I also tried FTP, which really isn't that bad as NAT-breaking
> protocols go. It didn't work because the server saw an illegal
> EPRT request. In IPv4 with NAT that wouldn't have happened
> because:
> 1. The FTP client would have used EPSV in order to be
> NAT-friendly, or
> 2. The FTP ALG would have intercepted the private address
> and rewritten it

No surprise here; exact same happened with NATv4 in the early stages. We
all know that NAT requires ALGs.

> Moral of the story: do IPv6 NAT at your peril.

Was the same with NATv4 too.

> Now of course it's possible to argue all of the stuff that
> makes IPv4 NAT work to the degree that it does today can also
> be added to IPv6, and that is true, strictly speaking.

Especially with the experience of doing it with v4.

> But will the vendors bother, and will the customers
> require it? I don't think so.

That's were you're wrong, IMHO. First, the vendors will do whatever the
customers want to buy, and customers are not always smart and will have
(Continue reading)

Mark Townsley | 3 Apr 17:20 2006
Picon

Re: Announcement of IAB member selection


Henrik Levkowetz wrote:
> I applaud the NomCom in this very appropriate choice -- at this particular
> time, I don't think there is any better choice they could possibly have
> made for the vacant IAB seat.  Bert has impressed me with his ability to
> always perceive where he is most needed, and appear there as if by magic
> to assist in whatever needs to be done.  I remember a thorny throughput
> issue we ran across some years ago at Casa de Bandini, when Bert came
> through as a trouper and helped us make headway with the problem [1].  With
> that taken care of, he also showed us his famous ability to make friends
> with the ladies [2].
> 
> We couldn't wish for a more well-rounded man of the world to step up to
> the plate and shoulder his responsibilities today.
> 
> 
> 	Henrik
> 
> 
> [1] http://tinyurl.com/jfsxm
> [2] http://tinyurl.com/zccdt

Or...

http://bert.secret-wg.org/Kisses/

> 
> 
> on 2006-04-01 04:15 Ralph Droms said the following:
> 
(Continue reading)

Henrik Levkowetz | 3 Apr 22:59 2006

Re: Announcement of IAB member selection

Mark,

on 2006-04-03 17:20 Mark Townsley said the following:
> 
> Henrik Levkowetz wrote:
>> I applaud the NomCom in this very appropriate choice -- at this particular
>> time, I don't think there is any better choice they could possibly have
>> made for the vacant IAB seat.  Bert has impressed me with his ability to
>> always perceive where he is most needed, and appear there as if by magic
>> to assist in whatever needs to be done.  I remember a thorny throughput
>> issue we ran across some years ago at Casa de Bandini, when Bert came
>> through as a trouper and helped us make headway with the problem [1].  With
>> that taken care of, he also showed us his famous ability to make friends
>> with the ladies [2].
>> 
>> We couldn't wish for a more well-rounded man of the world to step up to
>> the plate and shoulder his responsibilities today.
>> 
>> 
>> 	Henrik
>> 
>> 
>> [1] http://tinyurl.com/jfsxm
>> [2] http://tinyurl.com/zccdt
> 
> Or...
> 
> http://bert.secret-wg.org/Kisses/

Yes!  There you go!
(Continue reading)

Hallam-Baker, Phillip | 4 Apr 05:58 2006
Picon

RE: Announcement of IAB member selection

Looks like some of his opponents tried some underhand tactics though...

http://www.mlcsmith.com/humor/bertsama/ 

> -----Original Message-----
> From: Henrik Levkowetz [mailto:henrik <at> levkowetz.com] 
> Sent: Monday, April 03, 2006 4:59 PM
> To: Mark Townsley
> Cc: ietf <at> ietf.org
> Subject: Re: Announcement of IAB member selection
> 
> Mark,
> 
> on 2006-04-03 17:20 Mark Townsley said the following:
> > 
> > Henrik Levkowetz wrote:
> >> I applaud the NomCom in this very appropriate choice -- at this 
> >> particular time, I don't think there is any better choice 
> they could 
> >> possibly have made for the vacant IAB seat.  Bert has impressed me 
> >> with his ability to always perceive where he is most needed, and 
> >> appear there as if by magic to assist in whatever needs to 
> be done.  
> >> I remember a thorny throughput issue we ran across some 
> years ago at 
> >> Casa de Bandini, when Bert came through as a trouper and helped us 
> >> make headway with the problem [1].  With that taken care 
> of, he also 
> >> showed us his famous ability to make friends with the ladies [2].
> >> 
(Continue reading)

Jeffrey Hutzelman | 4 Apr 20:25 2006
Picon

Re: Last Call: 'TLS User Mapping Extension' to Proposed Standard


On Thursday, March 30, 2006 06:00:36 PM +0200 Simon Josefsson 
<jas <at> extundo.com> wrote:

> http://www.ietf.org/internet-drafts/draft-santesson-tls-ume-04.txt says:
>
>    This document does not specify how the server stores the
>    user_principal_name, or how exactly it might be used to locate a
>    certificate.  For instance, it might be appropriate to do a case-
>    insensitive lookup.  It is RECOMMENDED that the server processes the
>    user_principal_name with a stringprep profile [N7] appropriate for
>    the identity in question, such as Nameprep [N8] for the portion
>    domain portion of UPN, SASLprep [N9] for the user portion of the UPN
>    and stringprep appendix B.3 [N7] as mapping table for case folding.
>
> Given that the first and second sentence make it clear that the use of
> StringPrep is not required, I suggest using MAY instead of RECOMMENDED
> in the third sentence.  RECOMMENDED is the same as SHOULD according to
> RFC 2119, and is a fairly strong recommendation.  Its use seem
> misplaced here.

Right.  RECOMMENDED does not mean "we think this is a good idea".  It means 
something more like "you have to do this or have a good reason not to".

> It may be better to avoid RFC 2119 language completely here, because
> the entire paragraph is merely an example of what you can do.

Agree.  RFC2119 language has no place in a "for instance".

_______________________________________________
(Continue reading)

Johan Bosaeus | 5 Apr 11:40 2006

Syslog inquiry, TAG delimiters.

Hello,
We got a problem interpreting the RFC 3164 and we would appreciate any 
comments of the issue of what is a valid TAG delimiter.

First, last part of section 4.1.3 states:

"   The MSG part has two fields known as the TAG field and the CONTENT
   field.  The value in the TAG field will be the name of the program or
   process that generated the message.  The CONTENT contains the details
   of the message.  This has traditionally been a freeform message that
   gives some detailed information of the event.  The TAG is a string of
   ABNF alphanumeric characters that MUST NOT exceed 32 characters.  Any
   non-alphanumeric character will terminate the TAG field and will be
   assumed to be the starting character of the CONTENT field.  Most
   commonly, the first character of the CONTENT field that signifies the

   conclusion of the TAG field has been seen to be the left square
   bracket character ("["), a colon character (":"), or a space
   character.  This is explained in more detail in Section 5.3."

This part implies that "space" is a legal character to terminate a TAG with. 
However, further down in the text, section "5.4 Examples", you will find:

"
       Use the BFG!

   While this is a valid message, it has extraordinarily little useful
   information.  This message does not have any discernable PRI part. It
   does not contain a timestamp or any indication of the source of the
   message.  If this message is stored on paper or disk, subsequent
(Continue reading)

Lars-Erik Jonsson (LU/EAB | 5 Apr 15:32 2006
Picon

RE: Stupid NAT tricks and how to stop them.

> From: Michel Py [mailto:michel <at> arneill-py.sacramento.ca.us]
> Unfortunately some protocol purity zealots still have to realize
> that Linksys, Netgear, Belkin and consorts don't sell NAT boxes
> because they think NAT is good, they sell NAT boxes because
> consumers want to buy them. 

I do not think consumers in general want to buy NAT boxes, but
they are forced to do so by ISP's who do not give them a choice.

When not even those of us who can differentiate between different
Internet connections by other means then "speed" can manage to get
a proper Internet connection (e.g. with multiple fixed addresses),
how can we expect regular users to ask for such "advanced" features?

Myself, I am stuck with a telco-ISP that do not even provide
the option to buy extra IP-addresses (or fixed addresses). This
means I am forced to run a NAT at home, and do the tricks to 
make applications work in this environment (including making
servers work, which of course "is not allowed", but why should I
care).

At several occasions, friends have asked me why some of their
communications applications do not work although they have "a
premium Internet connection", which meant they had purchased
the highest "speed" available. Unfortunately, they have all
been fooled by the ISPs that the only difference between different
Internet connections is the maximal throughput, and they have
ended up in a crappy NETed home environment.

But why should ISPs be honest and explain to regular users 
(Continue reading)


Gmane