Martin Stiemerling | 21 Oct 12:08 2014
Picon

Re: [dtn] proposed DTN workgroup - what is process being followed?

Hi Lloyd,

Thanks for sharing your concerns and see my replies in the text below:

Am 18.10.14 um 16:27 schrieb Lloyd Wood:
>
>
>
> I see that the Hawaii IETF 91 agenda is out:
> https://datatracker.ietf.org/meeting/91/agenda.txt
> This lists a DTN WG meeting on the Thursday.

It is listed as a WG, as it is expected to be a WG by the start of the 
IETF-91 meeting. Right now, DTN is still in the stage of a proposed 
Working Group, i.e., the final decision if there will be a DTN working 
group is still to be made.

The draft charter for external review has just been sent out on 10/22.

>
> I am somewhat puzzled by this, as I was under the impression that
> discussion of whether to form a DTN workgroup or not was still underway;
> I thought it was currently blocked.
> https://datatracker.ietf.org/doc/charter-ietf-dtn/ballot/

The charter is not blocked anymore, as the concerns in the IESG got 
resolved.

I am not sure how to arrive at the impression that the formation of a 
DTN WG is blocked in principle. My personal impression from the BOF 
(Continue reading)

S Moonesamy | 20 Oct 01:28 2014

Re: Media type for PGP message?

Hi Tim,
At 08:10 17-10-2014, Tim Bray wrote:
>I'm actually a little out of touch with the drill on a media-type
>registration daft.  Does it need a WG?

The short answer is no.

You could send the registration request (RFC 6838) to 
https://www.ietf.org/mailman/listinfo/media-types and run the draft 
through apps-discuss <at> ietf.org if you are aiming for a RFC.  I suggest 
contacting one of the Application Area Directors for the process details.

Regards,
S. Moonesamy 

Jari Arkko | 19 Oct 07:47 2014
Picon

Re: proposed DTN workgroup - what is process being followed?

Lloyd,

Good question. It is customary that working groups being proposed to be created (like DTN is) are given a
slot in the schedule. If the working group creation goes through before the meeting, the slot will be a
regular working group meeting. If it does not go through, depending on circumstances we’d either run
the meeting as a BOF or cancel it.

That was the process part. I’ll let others comment on the substance part of your comments.

Jari

IETF Chair | 18 Oct 05:38 2014
Picon

Budget and fees for 2015

Some time ago we asked the community about IETF meeting fees and the possible
need to raise them due to increasing costs. 

I wanted to inform you that this week the IAOC has adopted the IETF 2015 budget
and 2016 - 2017 budget projections. The budget has been submitted to ISOC
as a part of their overall budget process that is ongoing. 

All information is available at

  https://iaoc.ietf.org/2015-budget.html

The budget includes the increased registration fees from 2014 to 2015 as follows:

Early Bird               $650 to $700
Late Registration    $800 to $875
Day Pass                $350 to $375
Student (Full Time) $150 to $150

Jari Arkko
IETF Chair

Ole Jacobsen | 18 Oct 03:32 2014

*** Reminder and update "Nerds in Paradise" T-shirts ***


**** UPDATE: We will offer women's style T-shirts as well as the 
originally announced range of sizes. If you have already ordered
and would like to make a change, please respond with the details.

**** REMINDER: The deadline is approaching, send in your order today!

Dear IETF 91 Attendee,

Twenty-five years ago, the IETF met in Honolulu for IETF 15. This was 
long before the days of hosts and sponsors and thus long before there 
were any official T-shirts for attendees.

A small group of IETFers got together and decided that it would be fun 
to create a T-shirt. The now-famous "Nerds in Paradise" imprint was 
designed by Julia Topolcic and became, as far as we know, the first 
IETF shirt ever. It was printed locally in Honolulu and distributed to 
those who had signed up for it.

This is what the shirt looked like: 

http://www.blkk.com/_Media/img_4721-2.jpeg

To commemorate IETF 15 and that T-shirt, we are planning to produce a 
Version 2.0 in the same ad hoc fashion, based closely on the original 
design. The cost per T-shirt will about US $ 15.00, priced to offset 
the cost of this excercise. The final price will depend on how many 
shirts we order. If there are surplus funds, we will donate them to 
the Open Internet Endowment:

(Continue reading)

IETF Agenda | 18 Oct 02:25 2014
Picon

IETF 91 Final Agenda

91st IETF Meeting - Honolulu, HI, USA
November 9 - 14, 2014

The final agenda is now available.

https://datatracker.ietf.org/meeting/91/agenda.html
https://datatracker.ietf.org/meeting/91/agenda.txt

While this is considered the final agenda for printing, changes may be made to the agenda up until and during
the meeting. Updates will be reflected on the web version of the agenda. 

Information about the 91st IETF meeting in Honolulu, HI, USA can be found here: https://www.ietf.org/meeting/91/index.html

Thank you and see you in Honolulu!

Sincerely,

The IETF Secretariat

IETF Chair | 18 Oct 02:01 2014
Picon

Area restructuring, and the open App AD position

For your information, this message was sent today to the Nomcom from the IESG, based on the decision that the IESG made in yesterday’s conference call.

Jari Arkko
IETF Chair

Begin forwarded message:

From: Barry Leiba <barryleiba <at> computer.org>
Subject: [IAB] Area restructuring, and the open App AD position
Date: 17 Oct 2014 16:50:13 PDT
To: nomcom14-coord <nomcom14-coord <at> ietf.org>, Michael Richardson <mcr+nomcom <at> sandelman.ca>
Cc: IAB <iab <at> iab.org>

Dear NomCom (Cc IAB),

As we indicated in our earlier message to the community, the IESG is planning to reorganise areas and working groups within areas. This is done to better match our structure to current topics in the IETF, and to increase our ability to deal with the naturally occurring fluctuations in the topic areas. While there are ideas about what this would mean in practice, our plan is to work within the IESG and the community in the coming months to come up with a detailed plan by May 2015. However, it seems clear to us that the reorganisation will affect the applications and real-time applications areas. The IETF remains working very actively on these areas, but it is expected that the number of area directors overseeing applications work can be smaller (and perhaps increase in other areas). The IESG is in charge of organising its work, and a part of that is proper matching management resources to current topic areas. The IESG felt that at this time, not filling the position of the other APP area director would be a prudent course of action. It would match our view about where the topic areas currently are at, would still retain sufficient expertise in the IESG, and would give maximum flexibility for making a restructuring decision in 2015.

We put the above information to the community, and there have been a number of concerns about telling you to simply not fill the position. Some comments indicated that we should ask you to fill it for a one year term, or that we should focus on other aspects of the IESG’s organisation, and so on. But we heard no concerns about undertaking the reorganization in principle. In the meantime, some willing nominees for the APP area position have surfaced.

As a result, the IESG would like to inform you that you (and the IAB as a confirming body) should choose to do what you decide is best. You can either fill the seat or not fill it. However, the IESG does believe that leaving the seat un-filled at this time would be the best course of action. If the seat is filled, the candidates should be aware that we think the skillset described in the desired qualifications is not accurate as it stands, and candidates should be prepared to help in the reorganization, which may end them up in a position with an as-yet-undefined set of skills and responsibilities. But again, we don't think it's strictly necessary that you fill the position.

Barry Leiba (Nomcom Liaison) for the IESG


IAB Chair | 17 Oct 20:26 2014

Call for Feedback on the current IRTF Chair

As part of its oversight responsibility for the Internet Research Task Force (IRTF), the IAB is soliciting
comments from the community on the performance of the IRTF Chair, Lars Eggert.  We are interested in
comments on what has gone well or badly in the last several years.  Lars has been serving in the IRTF Chair
position since March 2011.

RFC 2850 includes a paragraph about the selection of the IRTF Chair.  It says:

  3.3 Selection of the IRTF chair

  The IAB shall have the authority to appoint the chair of the Internet
  Research Task Force (IRTF) for a two-year renewable term, and to
  remove him or her. The IRTF chair shall be responsible for the
  management and organization of the IRTF according to [BCP 8].

Please send comments to iab-chair at iab.org and execd at iab.org.

We would appreciate receiving comments as soon as possible, as the IAB will likely begin the next steps in
the oversight process shortly after the end of IETF 91 in Honolulu.

Thank you,
  Russ Housley
  IAB Chair

Thomas Narten | 17 Oct 06:53 2014
Picon

Weekly posting summary for ietf <at> ietf.org

Total of 107 messages in the last 7 days.

script run at: Fri Oct 17 00:53:02 EDT 2014

    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 12.15% |   13 |  9.59% |    97535 | phill <at> hallambaker.com
  7.48% |    8 |  6.85% |    69695 | john-ietf <at> jck.com
  3.74% |    4 |  6.56% |    66689 | jg <at> freedesktop.org
  5.61% |    6 |  4.31% |    43839 | jari.arkko <at> piuha.net
  4.67% |    5 |  4.40% |    44733 | mstjohns <at> comcast.net
  3.74% |    4 |  4.56% |    46422 | harald <at> alvestrand.no
  3.74% |    4 |  4.45% |    45272 | tbray <at> textuality.com
  2.80% |    3 |  5.31% |    53992 | david.black <at> emc.com
  1.87% |    2 |  3.69% |    37553 | ian.farrer <at> telekom.de
  2.80% |    3 |  2.23% |    22719 | rjsparks <at> nostrum.com
  1.87% |    2 |  2.54% |    25807 | abdussalambaryun <at> gmail.com
  1.87% |    2 |  2.26% |    23026 | warren <at> kumari.net
  1.87% |    2 |  2.01% |    20477 | scott <at> kitterman.com
  1.87% |    2 |  1.87% |    19068 | sm+ietf <at> elandsys.com
  1.87% |    2 |  1.73% |    17633 | nomcom-chair-2014 <at> ietf.org
  1.87% |    2 |  1.70% |    17297 | presnick <at> qti.qualcomm.com
  1.87% |    2 |  1.67% |    17034 | stephen.farrell <at> cs.tcd.ie
  0.93% |    1 |  2.55% |    25967 | michael.jones <at> microsoft.com
  1.87% |    2 |  1.60% |    16264 | brian.e.carpenter <at> gmail.com
  1.87% |    2 |  1.60% |    16242 | joelja <at> bogus.com
  1.87% |    2 |  1.45% |    14738 | ned+ietf <at> mauve.mrochek.com
  1.87% |    2 |  1.44% |    14671 | vesely <at> tana.it
  0.93% |    1 |  2.36% |    23983 | dafalla <at> yahoo.com
  1.87% |    2 |  1.37% |    13919 | mcr+ietf <at> sandelman.ca
  1.87% |    2 |  1.28% |    13070 | mansaxel <at> besserwisser.org
  0.93% |    1 |  1.39% |    14153 | spencerdawkins.ietf <at> gmail.com
  0.93% |    1 |  1.17% |    11880 | dave <at> cridland.net
  0.93% |    1 |  1.01% |    10297 | narten <at> us.ibm.com
  0.93% |    1 |  0.99% |    10054 | phdgang <at> gmail.com
  0.93% |    1 |  0.93% |     9426 | superuser <at> gmail.com
  0.93% |    1 |  0.90% |     9202 | daedulus <at> btconnect.com
  0.93% |    1 |  0.89% |     9030 | lars <at> netapp.com
  0.93% |    1 |  0.85% |     8667 | eburger <at> standardstrack.com
  0.93% |    1 |  0.80% |     8148 | jiangsheng <at> huawei.com
  0.93% |    1 |  0.80% |     8131 | tjc <at> ecs.soton.ac.uk
  0.93% |    1 |  0.77% |     7860 | peter <at> akayla.com
  0.93% |    1 |  0.73% |     7393 | stbryant <at> cisco.com
  0.93% |    1 |  0.71% |     7209 | masinter <at> adobe.com
  0.93% |    1 |  0.71% |     7198 | jelte.jansen <at> sidn.nl
  0.93% |    1 |  0.68% |     6879 | melinda.shore <at> gmail.com
  0.93% |    1 |  0.67% |     6856 | olejacobsen <at> me.com
  0.93% |    1 |  0.66% |     6700 | dhc <at> dcrocker.net
  0.93% |    1 |  0.65% |     6656 | leslie <at> thinkingcat.com
  0.93% |    1 |  0.65% |     6614 | barryleiba <at> computer.org
  0.93% |    1 |  0.64% |     6554 | ted.lemon <at> nominum.com
  0.93% |    1 |  0.63% |     6375 | mohta <at> necom830.hpcl.titech.ac.jp
  0.93% |    1 |  0.62% |     6350 | fernando <at> gont.com.ar
  0.93% |    1 |  0.61% |     6244 | peter <at> andyet.net
  0.93% |    1 |  0.58% |     5929 | john <at> jlc.net
  0.93% |    1 |  0.55% |     5576 | ietf-secretariat <at> ietf.org
  0.93% |    1 |  0.54% |     5460 | johnl <at> taugh.com
  0.93% |    1 |  0.47% |     4822 | agenda <at> ietf.org
--------+------+--------+----------+------------------------
100.00% |  107 |100.00% |  1017308 | Total

Phillip Hallam-Baker | 16 Oct 21:50 2014

Software and Configuration Management Was: Local Cloud Node

I started to draft out my ideas under the impression that the cut off
date is tomorrow when there is a bit more time.

This is a starting point for a draft:

https://tools.ietf.org/html/draft-hallambaker-sxs-confirm-00

My home configuration has already exceeded the complexity of a typical
university department in the 1990s and it is far from comprehensive.
Less than a quarter of the light switches are under IP control. Such
organizations found software management and distribution
infrastructures essential so it is a good bet that the home will.

It will always be necessary to support the approach where the user
relies on a cloud service provided by the vendor. But it should also
be possible to bind a device to a local or personal 'hub' so that it
receives all its directions from that source. Including when to accept
updates, which updates to accept, etc. etc.

While the vulnerability concern is limited to 'software' (anything
from HTML to firmware), the line between software and configuration is
blurred. Especially when many vulnerabilities are configuration
settings. So configuration is also part of the issue here.

Peter Saint-Andre - &yet | 15 Oct 04:15 2014
Picon

"Jabber Scribe" howto

FYI, today I published an I-D that provides a few suggestions for 
fulfilling the role of a "Jabber Scribe" during IETF meetings:

http://datatracker.ietf.org/doc/draft-saintandre-chatroom-relay/

Feedback is welcome. (Please send it to me directly or cc me, since I am 
not subscribed to the ietf <at> ietf.org list.)

Thanks!

Peter

--

-- 
Peter Saint-Andre
https://andyet.com/


Gmane