On 8/13/2012 7:14 AM, philip.eard...@bt.com wrote:
Ben,
Thanks for your review.
The right status isn't clear-cut (I think), but when we (Chairs & Wes)
discussed it, Info seemed best
* mainly because precedent seems to be that API docs are informational, for
example socket API extensions for
The document says:
o Bullet 3, paragraph 1 is replaced by this:
The nominating committee comprises at least a Chair, 10 voting
volunteers, 4 liaisons, and an advisor.
The Past Chair is missing.
The adviser is not required, a
Behcet Sarikaya writes:
> It was a natural event that happens rarely in Dallas, in fact since
> 2006, it has not happened again.
That's because we haven't been back yet.
--
Wes Hardaker
SPARTA, Inc.
The document says:
o Bullet 15 is replaced by these two bullets:
15.1. Members of the Internet Society Board of Trustees and
sitting members of the IAB, the IESG, and the IAOC,
including
members
Hi,
I think very strongly that IAB should sign this document.
Cheers,
Jonne.
--
Jonne Soininen
Renesas Mobile
Tel: +358 40 527 4634
E-mail: jonne.soini...@renesasmobile.com
On 8/11/12 1:55 AM, "Bob Hinden" wrote:
>I support the IETF and IAB chairs signing document.
>
>Bob
>
>On Aug 10,
On 8/17/12 4:21 PM, Russ Housley wrote:
> The document says:
>
> o Bullet 15 is replaced by these two bullets:
>
> 15.1. Members of the Internet Society Board of Trustees and
> sitting members of the IAB, the IESG, and the IAOC,
--On Friday, August 17, 2012 10:05 -0400 Russ Housley
wrote:
> The document says:
>
> o Bullet 3, paragraph 1 is replaced by this:
>
>The nominating committee comprises at least a
> Chair, 10 voting volunteers, 4 liaisons,
At 07:05 17-08-2012, Russ Housley wrote:
The document says:
o Bullet 3, paragraph 1 is replaced by this:
The nominating committee comprises at least a
Chair, 10 voting
volunteers, 4 liaisons, and an advisor.
The Past Chair is missing.
The Past
--On Friday, August 17, 2012 10:05 -0400 Russ Housley
wrote:
> The document says:
>
> o Bullet 3, paragraph 1 is replaced by this:
>
>The nominating committee comprises at least a
> Chair, 10 voting volunteers, 4 liaisons,
Russ has raised a couple of good points. I like John's solution to
one of them, and SM has proposed a good solution to the other off
list. I have the following changes in the pending next version.
I've slightly edited John's text, and Section 4, bullet 3, paragraph 1
will now change to this:
Hi Bob,
Is there any way to broaden the scope of IAOC choice and provide the
candidate locations which would meet IETF criteria by any IETF member ?
For example once I know the criteria I could check around in Poland to
see if there is any place which would satisfy the future IETF venue.
I
On 8/17/12 12:05 PM, Robert Raszuk wrote:
Hi Bob,
Is there any way to broaden the scope of IAOC choice and provide the
candidate locations which would meet IETF criteria by any IETF member ?
For example once I know the criteria I could check around in Poland to
see if there is any place whic
> Hotel contracts by their nature need to be negotiated under mutual
> NDA unless you want all the vendors in the region to mysteriously
> arrive at the same lower bound.
All hotel rates are wide open and published on IETF web page. It's an
interesting NDA which permits open disclosure ;-)
Be
The advisor is the Immediately previous chair, or a member of the previous
noncom designated by that chair if he/she declines to serve or is otherwise
unavailable.
Sent from my iPad
On Aug 17, 2012, at 12:09, John C Klensin wrote:
>
>
> --On Friday, August 17, 2012 10:05 -0400 Russ Housley
--On Friday, August 17, 2012 15:05 -0400 Barry Leiba
wrote:
> Russ has raised a couple of good points. I like John's
> solution to one of them, and SM has proposed a good solution
> to the other off list. I have the following changes in the
> pending next version.
>
> I've slightly edited Jo
--On Friday, August 17, 2012 15:30 -0400 Michael StJohns
wrote:
> The advisor is the Immediately previous chair, or a member of
> the previous noncom designated by that chair if he/she
> declines to serve or is otherwise unavailable.
That was what I thought until I reread 3777. It says that
On 8/17/12 12:20 PM, Robert Raszuk wrote:
> Hotel contracts by their nature need to be negotiated under mutual
> NDA unless you want all the vendors in the region to mysteriously
> arrive at the same lower bound.
All hotel rates are wide open and published on IETF web page. It's an
interesting
Hi -
Is anyone tracking the number of interim meetings? It seems as
if the number has been growing quite a bit, although that may be
a function of the number of working groups. It might be
interesting to try to get a handle on whether or not there's been
some sort of shift in working methods wi
Barry, SM,
Given what started as a simple change has turned into many changes (14 changed
paragraphs by my count), I am starting to think that doing a RFC3777 update
document would be a better approach. Then it would be easy to look at a diff
from RFC3777 and see all of the changes.
Bob
On A
--On Friday, August 17, 2012 21:20 +0200 Robert Raszuk
wrote:
> Besides hotel is least worry as we do know the IETF rates for
> the last few years and it is quite easy to check with any
> hotel if they are willing to meet those targets or not.
Actually, we don't (although one can deduce a lot
Hi Bob,
At 13:24 17-08-2012, Bob Hinden wrote:
Given what started as a simple change has turned into many changes
(14 changed paragraphs by my count), I am starting to think that
doing a RFC3777 update document would be a better approach. Then it
would be easy to look at a diff from RFC3777 an
SM,
On Aug 17, 2012, at 1:44 PM, S Moonesamy wrote:
> Hi Bob,
> At 13:24 17-08-2012, Bob Hinden wrote:
>> Given what started as a simple change has turned into many changes (14
>> changed paragraphs by my count), I am starting to think that doing a RFC3777
>> update document would be a better a
Hi Bob,
At 13:53 17-08-2012, Bob Hinden wrote:
Yes, it would help for reviewing this draft, but it will still make
it complicated for future noncom's to understand the rules. A
single document would be easier to understand.
Ok. I'll post a draft.
I suppose an alternative would be to file an
>> The document says:
>>
>> o Bullet 3, paragraph 1 is replaced by this:
>>
>> The nominating committee comprises at least a
>> Chair, 10 voting volunteers, 4 liaisons, and an
>> advisor.
>>
>> The Past Chair is missing.
>>
>> Th
--On Friday, August 17, 2012 16:44 -0400 Dave Crocker
wrote:
>> --On Friday, August 17, 2012 21:20 +0200 Robert Raszuk
>> wrote:
>>
>>> Besides hotel is least worry as we do know the IETF rates for
>>> the last few years and it is quite easy to check with any
>>> hotel if they are willing to
Read section 10, 3rd paragraph of RFC3777.
> The prior year's Chair may select a designee from a pool composed of the
> voting
> volunteers of the prior year's committee and all prior Chairs if the Chair is
> unavailable.
> If the prior year's Chair is unavailable or is unable or unwilling to
On Fri, 17 Aug 2012, joel jaeggli wrote:
> On 8/17/12 12:20 PM, Robert Raszuk wrote:
> >
> > > Hotel contracts by their nature need to be negotiated under mutual
> > > NDA unless you want all the vendors in the region to mysteriously
> > > arrive at the same lower bound.
> >
> > All hotel rate
27 matches
Mail list logo
