IAB report to the community for IETF 120

[IAB Chair]

Hello everyone,

I’m happy to share the IAB’s report to the community for IETF 120, which has 
been posted to the datatracker here:

https://datatracker.ietf.org/meeting/120/materials/slides-120-ietf-sessa-iab-report-to-the-community-for-ietf-120-00

Some particular highlights:

IAB Workshop on AI-CONTROL
---
The IAB will be hosting an in-person workshop in September to discuss 
mechanisms to allow data on the Internet to opt-out of being used by 
AI-oriented crawlers. Those wishing to attend should send a position paper to 
ai-control-workshop...@iab.org <mailto:ai-control-workshop...@iab.org> by 
2024-08-02.

Details about the workshop can be found here: 
https://datatracker.ietf.org/group/aicontrolws/about/

New Work Help Desk
---
Some members of the IAB will be staffing a help desk in the IETF 120 
registration area during the week, particularly on Monday and Thursday 
afternoon. Please drop by if you have any questions about how to get new work 
started in the IETF, please drop by and chat with us!

We look forward to discussing these topics and more at our upcoming IAB Open 
session, which will take place on Thursday of the IETF 120 meeting!

Best,
Tommy Pauly
IAB Chair
On behalf of the IAB___
IETF-Announce mailing list -- ietf-announce@ietf.org
To unsubscribe send an email to ietf-announce-le...@ietf.org

IAB report to the community for IETF 119

[IAB Chair]

Dear Colleagues,

First, apologies for sending this report out late. Apparently it was stuck in 
my outbox.

The IAB has uploaded its report for the IETF 119 meeting to the proceedings in 
the datatracker. To access the full report, please see here:

https://datatracker.ietf.org/meeting/119/materials/slides-119-ietf-sessa-iab-report-to-the-community-for-ietf-119-00.pdf


In addition, I would like to highlight some recent/on-going activities:


New IAB webpage

The IAB has a new webpage! Note that some information, like IAB statements, has 
moved to the datatracker but is, of course, linked from the webpage. We hope 
that the new webpage and content rearrangement make it easier to find the 
information you need and improve record holding in general. Any feedback or 
comments on the new webpage are welcome! 


IAB workshop on Barriers to Internet Access of Services (BIAS)

The IAB held its Barriers for Internet Access of Services (BIAS) fully online 
workshop during the week of January 15, 2024, covering three sessions on 
community networks, digital divide, and censorship. 
Dhurv, as one of the chairs, wrote a nice blog post that I recommend; see here: 
https://www.ietf.org/blog/iab-bias-workshop/
The first draft of the workshop report has been published here: 
https://www.ietf.org/archive/id/draft-iab-bias-workshop-report-00.html
For further information on the workshop see: 
https://datatracker.ietf.org/group/biasws/about/


Interim meetings of IAB Technical Program on Environmental Impacts of Internet 
Technology (eimpact)
-
The IAB started last year a new program on Environmental Impacts of Internet 
Technology (eimpact) as a venue for discussing environmental impacts and 
sustainability of Internet technology. The program held a first meeting during 
IETF-118 and two interim online sessions on Feb 15 and 16. Find further 
information and all material here: 
https://datatracker.ietf.org/program/eimpact/meetings/
If you are interested, join the program’s a public mailing: e-imp...@ietf.org 
<mailto:e-imp...@ietf.org>

 

If you have any questions, comments, or concerns regarding the report or 
anything else, please send a mail to i...@iab.org <mailto:i...@iab.org>. Or 
feel free to also just send me an email directly!

Hope to see you all at IETF 119 either in person or online, at the IAB Open on 
Wednesday, or in the hallways and sessions!

Best regards,
Mirja Kühlewind
IAB Chair
On behalf of the IAB 


___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

IAB Outreach Coordinator role established

[IAB Chair]

The IAB has created a new IAB Outreach Coordinator role as part of our effort 
to better plan, coordinate, and keep track of the Outreach activities 
undertaken by the IETF Leadership. The coordinator will cooperate with the IESG 
and coordinate with the EODIR in tracking outreach activities.  
 
The IAB Outreach Coordinator can be contacted by sending mail to 
outre...@iab.org

The IAB has selected Dhruv Dhody to serve in the IAB Outreach Coordinator role 
for this year.  The IAB will annually reevaluate who is selected to serve in 
this role during the March IETF when all the IAB roles are assigned. 

If you have any comments or questions about these activities, feel to contact 
the IAB Outreach Coordinator, the IAB , or also me directly 
.

Mirja Kühlewind
IAB Chair
For the IAB

___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

IAB report to the community for IETF 117

[IAB Chair]

Dear Colleagues,

the IAB has uploaded its report for the IETF 117 meeting to the proceedings in 
the datatracker. To access the full report, please see here:

https://datatracker.ietf.org/meeting/117/materials/slides-117-ietf-sessc-iab-report-to-the-community-for-ietf-117-01


In addition, I would like to highlight some recent/on-going activities:


Proposed IAB program on Wholistic Human-Oriented Discussions on Identity 
Systems (WHODIS)

The IAB is considering a new program on Wholistic Human-Oriented Discussions on 
Identity Systems (WHODIS) and is currently soliciting community feedback, see 
here for the proposed program description:
https://github.com/intarchboard/proposed-program-whodis

You can provide comments or any kind of feedback directly in GitHub or by mail 
to either architecture-disc...@iab.org <mailto:architecture-disc...@iab.org> or 
directly to the IAB at i...@iab.org <mailto:i...@iab.org>.
Further, this is on the agenda to discuss during the IAB Open Meeting at IETF 
117 <https://datatracker.ietf.org/doc/agenda-117-iabopen/>, Tuesday July 25, 
13:00-14:30, Room Continental 5.


RFC9419 and RFC9413 published
-
The IAB recently published two new RFCs providing protocol design guidance for 
network-application collaboration on path signals as well as guidance on use of 
active protocol maintenance to increase robustness:
https://datatracker.ietf.org/doc/rfc9419/ (Considerations on Application - 
Network Collaboration Using Path Signals)
https://datatracker.ietf.org/doc/rfc9413/ (Maintaining Robust Protocols)


RIPE86 presentation
--
Some members of the IAB and IESG organised a BoF at RIPE86 to present an IETF 
Overview of Technical Work and Hot Topics. See the RIPE86 page for the slides 
and the recording:
https://ripe86.ripe.net/programme/meeting-plan/bof/
 

If you have any questions, comments, or concerns regarding the report or 
anything else, please send a mail to i...@iab.org <mailto:i...@iab.org>. Or 
feel free to also just send me an email directly!

Hope to see you all at IETF 117 either in person or online, at the IAB Open on 
Tuesday, or in the hallways and sessions!

Best regards,
Mirja Kühlewind
IAB Chair
On behalf of the IAB ___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

IAB report to the community for IETF 116

[IAB Chair]

Dear Colleagues,

the IAB has uploaded its report for the IETF-116 meeting to the proceedings in 
the datatracker. To access the full report, please see here:

https://datatracker.ietf.org/meeting/116/materials/slides-116-ietf-sessb-iab-report-to-the-community-for-ietf-116-00


In addition, I would like to highlight some recent/on-going/up-coming 
activities:


New workshop reports for M-TEN and e-impact

The IAB held end of last year two workshops and the initial version of the 
reports for both workshops has recently been published as drafts:
Report from the IAB workshop on Management Techniques in Encrypted Networks 
(M-TEN): https://datatracker.ietf.org/doc/draft-iab-m-ten-workshop/
Report from the IAB Workshop on Environmental Impact of Internet Applications 
and Systems, 2022: 
https://datatracker.ietf.org/doc/draft-iab-ws-environmental-impacts-report/

We will also present a report from the e-impact workshop in the IAB Open 
meeting on Thursday, March 30, Session III, 15:00-16:00 in room G401-G402. 
Please come and join us!


Liaison Coordination Office Hours - Thu 11:30-13:00 JST IAB Office

The IAB liaison coordinators will hold office hours on Thursday, March 30, 
during the lunch break 11:30-13:00 JST in the IAB Office (G318). We are 
offering this for the first time in order to give liaison managers as well as 
the community an opportunity to discuss any liaison management related question 
with us. Please come and join if you have any questions or concerns to discuss!


IAB Comments

The IAB has recently submitted multiple comments as input to public requests 
for feedback, e.g.
IAB Responds to Call for Input on “The relationship between human rights and 
technical standard-setting processes for new and emerging digital technologies”:
https://www.iab.org/2023/03/03/iab-responds-to-call-for-input-on-the-relationship-between-human-rights-and-technical-standard-setting-processes-for-new-and-emerging-digital-technologies/
IAB Comments on a notice by the Federal Trade Commission on “Trade Regulation 
Rule on Commercial Surveillance and Data Security” (16 CFR Part 464):
https://www.iab.org/2022/11/21/iab-comments-on-a-notice-by-the-federal-trade-commission-on-trade-regulation-rule-on-commercial-surveillance-and-data-security-16-cfr-part-464/
More generally, the IAB observes increased attention by regulators and 
policymakers to Internet-related topics due to the growing importance of the 
Internet. The IAB is working closely with ISOC and supports their efforts by 
submitting our own statements directly from the IAB in cases where we see a 
potentially high importance and potential impact on the Internet architecture.


If you have any questions, comments, or concerns regarding the report or 
anything else, please send a mail to i...@iab.org <mailto:i...@iab.org>. Or 
feel free to also just send me an email directly!

Hope to see you all at IETF-116 either in person or online, at the IAB Open on 
Thursday, or in the hallways and sessions!

Best regards,
Mirja Kühlewind
IAB Chair
On behalf of the IAB 


___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

IAB report to the community for IETF 115

[IAB Chair]

Dear Colleagues,

the IAB has uploaded its report for the IETF-115 meeting to the proceedings in 
the datatracker. To access the full report, please see here:

https://datatracker.ietf.org/meeting/115/materials/slides-115-ietf-sessa-iab-report-to-the-community-for-ietf-115-00
 
<https://datatracker.ietf.org/meeting/115/materials/slides-115-ietf-sessa-iab-report-to-the-community-for-ietf-115-00>


In addition, I would like to highlight some recent/on-going activities:


Invited talks in IAB Open on the role of technology in the protest crisis in 
Iran

The IAB Open meeting for 115 will host two invited talks: Mahsa Alimardani of 
the Oxford Internet Institute and ARTICLE 19 will discuss how Internet 
connectivity and digital technology can support Iran protesters, and Simone 
Basso from the Open Observatory of Network Interference (OONI) will present on 
their censorship measurements in Iran.


IAB workshop on Environmental Impact of Internet Applications and Systems in 
Dec - Upcoming deadline Nov 7
-
Coming up really soon the IAB will be holding an online workshop on 
Environmental Impact of Internet Applications and Systems 
<https://www.iab.org/activities/workshops/e-impact/> in the week of 5 December 
2022. The call for contributions will close on Nov 7. But that means you can 
still submit a position paper if you are interested in participating! Just be 
quick!


IAB Workshop on Management Techniques in Encrypted Networks (M-TEN)  on Oct 
17-19, 2022

The IAB held a workshop on Management Techniques in Encrypted Networks (M-TEN) 
<https://www.iab.org/activities/workshops/m-ten/> in October. All accepted 
position papers are available on the webpage. The recordings are available on 
YouTube. A first draft of the workshop report is expected soon. Slides are 
available in the datatracker: 
https://datatracker.ietf.org/team/mtenws/meetings/ 
<https://datatracker.ietf.org/team/mtenws/meetings/>


If you have any questions, comments, or concerns regarding the report or 
anything else, please send a mail to i...@iab.org <mailto:i...@iab.org>. Or 
feel free to also just send me an email directly!

Hope to see you all at IETF-115 either in person or online, at the IABopen on 
Tuesday, or in the hallways and sessions!

Best regards,
Mirja Kühlewind
IAB Chair
On behalf of the IAB 


___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

REMINDER: IETF 115 Hotel Room Block and Standard Registration Deadlines Approaching

[IAB Chair]

IETF 115
London and online
November 5-11, 2022
Hosted by Cisco

1.  Registration
2.  Reservations
3.  Fee Waivers
4.  Child Care
5.  IETF 115 Meeting T-Shirts
6.  Hackathon 
7. Social Event


1. Standard Registration Deadline:
The Standard deadline for registration is Monday, October 24th, UTC 23:59. Be 
sure to register before the deadline passes! Register online at: 
https://registration.ietf.org/115/

Standard Registration Full Week Rates:
Onsite Standard Registration: USD 875 + VAT, if paid in full prior to 23:59 UTC 
2022-10-24
Remote Standard Registration: USD 375, if paid in full prior to 23:59 UTC 
2022-10-24

NOTE: Payment is required at the time of registration. The Standard 
registration fee is available until Monday, October 24th at UTC 23:59. After 
Monday at UTC 23:59, the registration fees will increase. Registration types 
and fee tiers are available at https://registration.ietf.org/115/

If you require any further information or assistance with registration then 
please feel free to contact us at supp...@ietf.org.

2. Reservations & Hotel Room Block Ending:
The IETF 115 meeting venue is the Hilton London Metropole.  As explained in the 
FAQ, you will need to register before you can reserve a guest room at the 
venue. A link to reserve a guest room will be sent to you after you register. 
The IETF Room Rate ends Saturday, 2022-10-22. Guests booking after this date 
will be subject to an increased nightly rate.
https://www.ietf.org/how/meetings/115/faq/

3.  Fee Waivers for Remote Participants: 
We understand that not everyone can afford the IETF 115 remote registration fee 
for a variety of reasons, including issues with income, employment status and 
employer support, and we do not want any of these to be a barrier to 
participation. If you cannot afford the remote registration fee, then please 
take this fee waiver option to ensure that you can participate:
https://www.ietf.org/forms/115-registration-fee-waiver/.


4. Child Care:
Thanks to the generous support of our Diversity & Inclusion Gold sponsors, 
Akamai, Cisco, and Huawei and Bronze sponsors Comcast, Identity Digital and 
Verisign, we will once again be offering onsite childcare at IETF 115 in 
London, UK. Childcare will be provided by Rose Event Nannies, a professional 
event childcare provider. This service is offered free of charge to registered 
IETF participants and initially provides space for up to ten children.  We 
strongly encourage advance sign up to give us sufficient time to investigate 
adding more space if this service becomes fully booked.
roseeventnannies.co.uk

Please see the online FAQ for more information and a link to the form to sign 
up. Additional information regarding daily activities available upon request.
https://www.ietf.org/how/meetings/115/childcare/

 
5. IETF 115 Meeting T-Shirts:
Thanks to the generosity of the IETF 115 meeting host, Cisco, registered 
participants, both onsite and remote, have the option to receive a free t-shirt 
with free delivery or collection onsite. Limited quantities are available on a 
first-come, first-served basis.


6.  Hackathon:
The IETF is holding a Hackathon to encourage developers to discuss, collaborate 
and develop utilities, ideas, sample code and solutions that show practical 
implementations of IETF standards.

When: Saturday, November 5, 2022 through Sunday, November 6, 2022
Signup for the Hackathon Onsite: 
https://registration.ietf.org/115/new/hackathon_onsite/
Signup for the Hackathon Remote: 
https://registration.ietf.org/115/new/hackathon_remote/
More information can be found here: 
https://www.ietf.org/how/runningcode/hackathons/115-hackathon/
Keep up to date by subscribing to: 
https://www.ietf.org/mailman/listinfo/hackathon

The Hackathon is free to attend and open to all. Extend the invitation to 
colleagues outside the IETF! Descriptions and information regarding the 
technologies for the hackathon are located on the IETF 115 Meeting Wiki: 
https://wiki.ietf.org/en/meeting/115/hackathon

Don’t see anything that interests you? Feel free to add your preferred 
technology to the list, sign up as its Champion and show up to work on it. 
Note: you must login to the wiki to add content. If you do add a new 
technology, we strongly suggest that you send an email to hackat...@ietf.org to 
let others know. You may generate interest in your technology, and find other 
people who want to contribute to it.


7. Social Event:
Participants will have the opportunity to attend a unique social event on 
Tuesday, Nov 8th, hosted by Cisco. A limited amount of tickets are available, 
so be sure to register before they’re gone. Additional information regarding 
the social event can be found via our Social Event Page: 
https://www.ietf.org/how/meetings/115/social/

___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

IAB report to the community for IETF 114

[IAB Chair]

Dear Colleagues,

the IAB has uploaded its report for the IETF-114 meeting to the proceedings in 
the datatracker. To access the full report, please see here:

https://datatracker.ietf.org/meeting/114/materials/slides-114-ietf-sessa-iab-report-to-the-community-for-ietf-114-00
 
<https://datatracker.ietf.org/meeting/114/materials/slides-114-ietf-sessa-iab-report-to-the-community-for-ietf-114-00>

In addition, I would like to highlight some news and open calls:


RFC Editor Model (Version 3) up and running

With the publication of RFC9280 the new RFC Editor Model (version 3) is done! 
Thanks to everybody who contributed and special thanks to the chairs of the RFC 
Editor Future Development Program, Eliot Lear and Brian Rose, and also Peter 
Saint-Andre as document editor. Also thanks to all members of RSOC, which has 
been, as well as the RFC Editor Future Development Program, now closed. And 
thanks to Pete Resnick and Eric Rescorla, who are now serving as chairs of the 
new RFC Series Working Group (RSWG), and to all of the other candidates for 
their willingness to serve the community in this position!


IAB Workshop on Management Techniques in Encrypted Networks (M-TEN) & Planned 
workshop on sustainability

The IAB is planning a workshop on Management Techniques in Encrypted Networks 
(M-TEN) in October. Find the full call for paper on the IAB page here: 
https://www.iab.org/activities/workshops/m-ten/ 
<https://www.iab.org/activities/workshops/m-ten/>

If you're interested in participating, please submit a proposal by 2022-08-19 
to mten-workshop...@iab.org <mailto:mten-workshop...@iab.org>. 

The IAB is also planning a workshop for later this year or early 2023 on 
measuring the environmental impact of Internet applications and systems. Stay 
tuned for more details!


Open positions - ISO/IEC JTC1 SC6 liaison manager 

The IAB has always some open positions to fill. Currently we are specifically 
looking for a new liaison manager to ISO/IEC JTC1 SC6. If you are interested, 
please send a brief note to liaison-coordinat...@iab.org 
<mailto:liaison-coordinat...@iab.org> that explains your interest, your 
background, availability to attend meetings, and whether you have any potential 
conflicts of interest!



If you have any questions, comments, or concerns regarding the report or 
anything else, please send a mail to i...@iab.org <mailto:i...@iab.org>. Or 
feel free to also just send me an email directly!

Hope to see you all at IETF-114 either in person or online, at the IABopen on 
Tuesday, or in the hallways and sessions!

Best regards,
Mirja Kühlewind
IAB Chair
On behalf of the IAB 


___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

IAB Comments on A Notice by the Federal Communications Commission on Secure Internet Routing, issued 03/11/2022

[IAB Chair]

On 8 April 2022, the IAB responded to the FCC’s request for comments on Secure 
Internet Routing [1]:
IAB Comments on A Notice by the Federal Communications Commission on Secure 
Internet Routing, issued 03/11/2022

The text of the statement is available at: 
https://www.iab.org/documents/correspondence-reports-documents/2022-2/iab-comments-on-a-notice-by-the-federal-communications-commission-on-secure-internet-routing-issued-03-11-2022/


[1] 
https://www.federalregister.gov/documents/2022/03/11/2022-05121/secure-internet-routing___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

IAB comment on Mandated Browser Root Certificates in the European Union’s eIDAS Regulation on the Internet

[IAB Chair]

On April 8 2022, the IAB published the statement “IAB comment on Mandated 
Browser Root Certificates in the European Union’s eIDAS Regulation on the 
Internet”.

The text of the statement is available at: 
https://www.iab.org/documents/correspondence-reports-documents/2022-2/iab-comment-on-mandated-browser-root-certificates-in-the-european-unions-eidas-regulation-on-the-internet/
 
___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

IAB report to the community for IETF 113

[IAB Chair]

Dear Colleagues,

the IAB has uploaded its report for the IETF-113 meeting to the proceedings in 
the datatracker. To access the full report, please see here:

https://datatracker.ietf.org/meeting/113/materials/slides-113-ietf-sessa-iab-report-to-the-community-for-ietf-113
 
<https://datatracker.ietf.org/meeting/113/materials/slides-113-ietf-sessa-iab-report-to-the-community-for-ietf-113>


In addition, I would like to highlight some important updates:


New Independent Submission Editor (ISE): Eliot Lear

The IAB appointed Eliot Lear as the new Independent Submission Editor (ISE). 
Welcome Eliot and thanks for serving the community in this role!

There was a very good set of candidates for this position and the IAB would 
also like to thank all volunteers that were nominated and willing to serve in 
this role!

Adrian Farrel decided to step down after serving four years as in this role. 
The IAB thanks Adrian for his service as the Independent Submissions Editor 
(ISE) and his enthusiastic engagement in this role, thereby supporting the IETF 
community to ensure that all voices can be heard!



RFC Editor Model (Version 3) ready for approval 

The RFC Editor Future Development Program 
(https://datatracker.ietf.org/group/rfcefdp/ 
<https://datatracker.ietf.org/group/rfcefdp/>) concluded its work and handed 
draft-iab-rfcefdp-rfced-model (RFC Editor Model (Version 3) to the IAB for 
progression an Informational RFC on the IAB stream in early February. After a 
four week community call, on 2022-03-09, the IAB reviewed 
draft-iab-rfcefdp-rfced-model-12. With consideration of all feedback in 
coordination with the program chairs, the document editor, and the program 
itself recently draft-iab-rfcefdp-rfced-model-13 was published that 
incorporates remaining editorial changes. 

The final version of the new RFC Editor Model (Version 3) will be approved and 
published together with three related documents in the the IETF stream: 
draft-carpenter-rfced-iab-charter (IAB Charter Update for RFC Editor Model), 
draft-rsalz-2028bis (Entities Involved in the IETF Standards Process), and 
draft-rosen-rfcefdp-update-2026 (RFC Series Responsibility Change). 

As part of the new RFC Editor Model (Version 3) 
<https://datatracker.ietf.org/doc/draft-iab-rfcefdp-rfced-model/>, the IAB and 
IESG are tasked with appointing one chair each to the RFC Series Working Group 
(RSWG). The IAB and IESG issued a joint call for nominations/volunteers for the 
RSWG Chairs 
<https://www.iab.org/2022/03/14/iab-and-iesg-search-for-rfc-series-working-group-rswg-chairs/>
 on 2022-03-14. If you are interested or would like to nominate someone, please 
send a message with the name and email address of the nominee to ex...@iab.org 
<mailto:ex...@iab.org>. The nominations deadline is 2022-04-18.


New IAB drafts: Report on Workshop on Analysing IETF Data (AID) and 
draft-iab-path-signals-collaboration-00

A draft of the workshop report for last November's IAB workshop on Analyzing 
IETF Data (AID) <https://www.iab.org/activities/workshops/aid/> has been 
submitted as draft-iab-aid-workshop. Niels ten Oever will present this report 
at the IABopen meeting on Thursday March 24, 13:00-14:00.

The IAB adopted a new document for consideration for publication on the IAB 
stream: draft-iab-path-signals-collaboration-00 (Considerations on Application 
- Network Collaboration Using Path Signals). Before adoption there was a 
community input call. Thanks to all who provided feedback! Further feedback is 
of course welcome at any time! To provide more comments on the document or the 
topic in general, please send mail either to architecture-disc...@iab.org 
<mailto:architecture-disc...@iab.org>, i...@iab.org <mailto:i...@iab.org>, or 
the authors directly!



If you have any questions, comments, or concerns regarding the report or 
anything else, please send a mail to i...@iab.org <mailto:i...@iab.org>. Or 
feel free to also just send me an email directly!

Hope to see you all at IETF-113 either in person or online. Don’t forget to 
join the IABopen meeting on Thursday!

Best regards,
Mirja Kühlewind
IAB Chair

On behalf of the IAB ___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

IAB report to the community for IETF 112

[IAB Chair]

Dear Colleagues,

the IAB has uploaded its report for the IETF-112 meeting to the proceedings in 
the datatracker. To access the full report, please see here:

https://datatracker.ietf.org/meeting/112/materials/slides-112-ietf-sessa-iab-report-to-the-community-for-ietf-112-00


As always in this mail I would like to highlight some recents activities:


IAB Workshop on Analysing IETF Data (AID): Nov 29- Dec 2, online

The IAB is organizing a workshop on Analysing IETF Data (AID) from Nov 29 to 
Dec 2, 2021. As previous workshops, this workshop will be online only, however, 
we are planning for discussion sessions on Monday and Thursday, while Tuesday 
and Wednesday will provide some time for a hackathon. The aim of this activity 
is to enable engineers and researchers  to mine the IETF’s data sources in 
order to explore trends and derive insights into the inner workings of the 
process of standardization, participation, and governance. 

The full agenda can be found on the IAB workshop webpage and all position 
papers will be published there in the next days: 
https://www.iab.org/activities/workshops/aid/


RFC Editor Future Development Program 
——
The RFC Editor Future Development Program, while hosted under the IAB umbrella, 
operates like an IETF working group in order to develop changes to how the RFC 
Editor function is managed, staffed, and overseen. Program has started the 
program last call for draft-iab-rfced-future-rfced-model to run until Nov 5, 
which will be followed by a wider community consultation.

Please review the draft and provide feedback on the mailing list: 
rfced-fut...@iab.org

The RFC Editor Future Development Program will also hold a meeting at IETF-112 
on Wednesday, Nov 10, 15:30 UCT+1. 

See also https://datatracker.ietf.org/group/rfcefdp/


Open Independent Submission Editor (ISE) position - Thanks to Adrian!

After serving four years as the Independent Submissions Editor (ISE), Adrian 
Farrel is planning to step down in February 2022. The IAB thanks Adrian for his 
service, and is now searching for candidates to fill the ISE role. Suggestions 
for candidates are welcome at ise-searc...@iab.org.



If you have any questions, comments, or concerns regarding the report or 
anything else, please send a mail to i...@iab.org. Or feel free to also just 
send me an email directly!

Hope to see you all also in the plenary this Wednesday and the IABopen meeting 
next week!

Best regards,
Mirja Kühlewind
IAB Chair

On behalf of the IAB

___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

Fwd: [Rfced-future] Upcoming Community Consultations on Next Generation RFC Model

[IAB Chair]

Dear colleagues,

I would like to draw your attention to the message below. The IAB RFC Series 
Editorial Future Development Program is about to finish its work and it's now a 
good time to review draft-iab-rfcefdp-rfced-model!

Please see below for further information!

Mirja



> Begin forwarded message:
> 
> From: Eliot Lear 
> Subject: [Rfced-future] Upcoming Community Consultations on Next Generation 
> RFC Model
> Date: 27. October 2021 at 14:12:47 CEST
> To: "irtf-disc...@irtf.org" , gendispa...@ietf.org, 
> The IETF List , rfc-inter...@ietf.org
> Cc: "rfced-fut...@iab.org" , Brian Rosen 
> 
> Reply-To: "rfced-fut...@iab.org" 
> 
> Dear colleagues,
> 
> In March of 2020 the IAB kicked off the RFC Series Editorial Future 
> Development Program, a program opened to the entire community, with an eye 
> toward reviewing the RFC Editor model found in 
> draft-iab-rfcefdp-rfced-model-05[1]. We are now coming to the conclusion of 
> our work, and the IAB will soon begin its formal consideration, which is 
> governed by RFC 4845[2]. Part of that process includes solicitation of 
> community input.
> 
> The program has developed an evolution of the RFC Editor Model and a small 
> change to the charter of the IAB. You can find this evolution in 
> draft-iab-rfcefdp-rfced-model-05 as well as two companion drafts[3,4,5]. This 
> draft brings together many different points of view, as you can see from the 
> mailing list archive[6].
> 
> Here are some of the proposed changes that you may wish to know:
> 
> The community oversees the evolution of the series by means of an open 
> working group. Proposed changes that reach rough consensus will be reviewed 
> by an RFC Series Approval Board (RSAB) that consists of the RSCE and people 
> representing the various streams.
> 
> The RFC Editor role is changing to that of a consulting editor (RFC Series 
> Consulting Editor or RSCE). In this model, an expert will provide guidance to 
> the community, the streams, and to the RPC to evolve the series.
> 
> The IAB will no longer manage or oversee the RFC series. The community and 
> the streams will do that. The IAB will continue to be in the appeal path if 
> there are disputes.
> 
> There are a lot of things that won't change. The RPC would continue to handle 
> day-to-day functions of the RFC Editor function, and authors should not see 
> any immediate change in terms of how RFCs are published. They continue to be 
> managed through the LLC. We will continue to benefit from the expertise of a 
> professional expert, now the RSCE.
> 
> Of course, there's a lot more detail that is specified in the drafts.
> 
> This is what will soon be put forth for your comments. In the meantime, even 
> though the formal comment period is not yet open, we invite you to review the 
> model now and bring whatever questions you might have to the program when we 
> meet on Wednesday, November 10th, at 14.30 GMT at the IETF meeting. Of course 
> you can also join the mailing list[7] and contribute your questions and 
> comments there.
> 
> On behalf of the program,
> 
> Brian and Eliot
> 
> [1] 
> https://www.iab.org/activities/programs/rfc-editor-future-development-program/
>  
> 
> [2] https://www.rfc-editor.org/rfc/rfc4845.html 
> 
> [3] https://datatracker.ietf.org/doc/html/draft-iab-rfcefdp-rfced-model-05 
> 
> [4] 
> https://datatracker.ietf.org/doc/html/draft-carpenter-rfced-iab-charter-03 
> 
> [5] https://datatracker.ietf.org/doc/html/draft-rosen-rfcefdp-update-2026-01 
> 
> [6] https://mailarchive.ietf.org/arch/browse/rfced-future/ 
> 
> [7] https://www.iab.org/mailman/listinfo/rfced-future 
> -- 
> Rfced-future mailing list
> rfced-fut...@iab.org
> https://www.iab.org/mailman/listinfo/rfced-future

___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

Thanks to Adrian Farrel for this service as ISE!

[IAB Chair]

Dear community members, dear Adrian,

As we recently announced, Adrian Farrel has informed us that he is not planning 
to serve in the role as Independent Submission Editor (ISE) for another term. 
Therefore, Adrian’s term is ending in February 2022 and the IAB has started the 
process of finding a replacement.

Adrian, the IAB would like to take this opportunity to thank you for your 
service! You’ve fulfilled this role enthusiastically for us. You have provided 
high value to our community as you have ensured that all voices can be heard. 
As such, you have used this role to be an advocate for inclusivity. While 
alternative opinions can sometimes cause tension, they make our community and 
our work better in the end. Thanks for everything you have done in the last 
(nearly) 4 years to improve the ISE function for our community!

I know you will keep serving our community with your expertise and I’m looking 
forward to see you at some point at our next non-online meeting again to say 
another thanks in-person!

Mirja Kühlewind
IAB Chair
For the IAB
___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

IAB report to the community for IETF 111

[IAB Chair]

Dear Colleagues,

the IAB has uploaded its report for the IETF-111 meeting to the proceedings in 
the datatracker. To access the full report, please see here:

https://datatracker.ietf.org/meeting/111/materials/slides-111-ietf-sessa-iab-report-to-the-community-for-ietf-111


In addition I would like to highlight some recents activities in this email:


IAB Workshop on Measuring Network Quality for End-Users


The IAB will hold a virtual workshop on Measuring Network Quality for End-Users 
on 14-16 September 2021. The focus of this workshop is to define properties and 
metrics with the goal of improving Internet access for all users. Interested 
participants are invited to submit position papers to 
network-quality-workshop...@iab.org by Monday, 2021-08-02.

See also https://www.iab.org/activities/workshops/network-quality/


RFC Editor Future Development Program 


The RFC Editor Future Development Program, while hosted under the IAB umbrella, 
operates like an IETF working group in order to develop changes to how the RFC 
Editor function is managed, staffed, and overseen. Participation is open to all 
and work is performed via email and frequent interim meetings. Recently the 
program has adopted draft-iab-rfcefdp-rfced-model and is now sneaking for 
reviews and broad input on the open issues.

See also https://datatracker.ietf.org/group/rfcefdp/



If you have any questions to the IAB, regarding the report or anything else, 
please send a mail to i...@iab.org. Or, feel free to also just send me an email 
directly, if you have any comments or concerns you want to discuss!

Hope to see you all also in the IABopen meeting or plenary next week, which 
both of course provide another opportunity to ask questions or provide input to 
the IAB!

Best regards,
Mirja Kühlewind
IAB Chair

On behalf of the IAB


___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

IAB Liaison Coordinator role established

[IAB Chair]

The IAB has created a new Liaison Coordinator role as part of our effort to 
remodel our internal handling of our liaison oversight responsibility. With 
this effort, the IAB aims to maintain a better overview of all on-going liaison 
activities, to provide our liaison managers with better support, and be more 
actively involved when necessary as well as be able to react quickly as needed. 

As already announced in the last IAB community report during IETF 110, this new 
role replaces the IAB's previous internal shepherding structure but it does not 
change the nature of the liaison management roles as performed by the liaison 
managers. This new role is specifically intended to clarify communication with 
liaison managers and the community by providing a single contact point within 
the IAB.  The Liaison Coordinator(s) can be contacted by sending mail to 
liaison-coordinat...@iab.org

The IAB has selected Wes Hardaker and Tommy Pauly to serve in the Liaison 
Coordinator role for the next year.  The IAB will annually reevaluate who is 
selected to serve in this role during the March IETF when all the IAB roles are 
assigned.  

As a next step, the Liaison Coordinators will also reach out to our liaison 
managers to advertise this change as well as collect input for other desired or 
needed improvements to the IAB's liaison responsibilities.

If you have any comments or questions about these activities, feel to contact 
the Liaison Coordinators, the IAB , or also me directly 
.

Mirja Kühlewind
IAB Chair
In the name of the IAB
___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

Contract with Temporary RFC Series Project Manager has been extended to March 2022

[IAB Chair]

The IAB has, based on the recommendation of RSOC, requested the Executive 
Director to extend the contract with the Temporary RFC Series Project Manager 
John Levine. The contract and SoW have been extended to March 2022 on the same 
terms and conditions. The Temporary RFC Series Project Manager is responsible 
for a subset of the tasks that are normally performed by the RFC Series Editor 
(RSE) while the RFC Editor Future Development Program is working on evolution 
of the RFC Editor model.

Thanks to John for supporting the community in this role!

Kind regards,
Mirja Kühlewind
IAB Chair on behalf of the IAB
___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

IAB report to the community for IETF 110

[IAB Chair]

Dear colleagues,

As usually, the IAB has uploaded its report for the IETF-110 meeting to the 
proceedings in the datatracker. To access the full report, please see here:

https://www.ietf.org/proceedings/110/slides/slides-110-ietf-sessa-iab-report-to-the-community-for-ietf-110-00


In this email I would also like to use the opportunity to highlight some news:

IAB Chair selection
——
The IAB has reselected me, Mirja Kühlewind, as IAB Chair. Thanks a lot! I’m 
really looking forward to serve another year in this role and to keep working 
with a new IAB on further improving transparency and visibility of the IAB 
hoping that we as a group can provide valuable input to the community!


Workshop reports
——
The IAB has published the draft workshop report for the COVID-19 Network 
Impacts IAB workshop that was held online last November:

https://datatracker.ietf.org/doc/draft-iab-covid19-workshop/

We already received quite some feedback and some good reviews. Huge thanks for 
that! We believe this document will soon after the IETF-110 meeting be ready 
for publication as IAB RFC. However, more feedback and reviews are of course 
very welcome!

Further, the report for the IAB workshop on Design Expectations vs. Deployment 
Reality in Protocol Development has been published as RFC 8980: 

https://datatracker.ietf.org/doc/rfc8980/


IAB Liaison Coordination
——
The IAB has established a new Liaison Coordinator position. This position 
provides a clear contact point for all liaison managers as well as for the 
community regarding any liaison-related requests towards the IAB. Further, this 
new role is a first step to improve coordination and communication of our 
liaison management and handling of liaison statements. The IAB is currently 
working actively on further improvements in that direction. 

To reach the IAB liaison coordinator(s) a new mailing alias has been 
established:

liaison-coordina...@iab.org


In any case, you can of course still reach the IAB with any questions, also 
regarding liaisons, directly by sending a mail to i...@iab.org.

Or, feel free to also just send me an email directly, if you have any comments 
or concerns you want to discuss!

Best regards,
Mirja Kühlewind
IAB Chair

On behalf of the IAB



___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

Re: IAB report to the community for IETF-109

[IAB Chair]

Hi all,

Sorry for sending the wrong link. Was a long week last week and this slipped 
through Friday night.

Thanks, Ole, for correcting this!

Mirja


> On 13. Nov 2020, at 19:40, Ole Jacobsen  wrote:
> 
> 
> The URL is wrong, it should be:
> 
> https://www.ietf.org/proceedings/109/slides/slides-109-ietf-sessa-iab-report-to-the-community-for-ietf-109-00
> 
> s/108/109/
> 
> 
>> On 13 Nov 2020, at 10:34, IAB Chair  wrote:
>> 
>> Dear colleagues,
>> 
>> As also done last time, we have uploaded the full report into the 
>> proceedings of the datatracker and this email will only summarise a few 
>> highlights.
>> 
>> To access the full report, please see here:
>> 
>> https://www.ietf.org/proceedings/108/slides/slides-108-ietf-sessa-iab-report-to-the-community-for-ietf-108-00
>> 
>> 
>> IAB Open Meeting
>> ——
>> The IAB will hold for the second time the IAB Open Meeting. The session will 
>> be Tuesday, November 17, 14:30 - 15:30 ICT (UTC +7).
>> 
>> This session is aiming to provide an opportunity for more direct 
>> interactions and technical discussion between the community and the IAB, in 
>> both directions: providing information about and reporting back on work 
>> done, as well as gathering input about on-going work.
>> 
>> The agenda is available here:
>> https://datatracker.ietf.org/meeting/108/materials/agenda-108-iabopen-01
>> 
>> 
>> IAB Workshop on COVID-19 Network Impacts
>> ——
>> The IAB has held a virtual workshop on Network Impacts by the COVID-19 
>> crisis this week, Nov 9-13, with in total three sessions on Mon, Wed, Fri. 
>> Recording are online:
>> 
>> Session 1 - Measurement and Observation: https://youtu.be/RTJNaE7TnGA
>> Session 2 - Operational Issue: https://youtu.be/tleJg1_SGXM
>> Session 3 - Future/Conclusions/Parking Lot: https://youtu.be/KCwUBQAkEww
>> 
>> A report is work-in-progress and will be published by the IAB.
>> 
>> 
>> IAB Programs
>> ——
>> The IAB has been working on refactoring its programs. In analysing the 
>> current IAB programs, the IAB identified two kinds of programs which are 
>> quite different in their needs and goals. Therefore, the new structure 
>> proposes to separate today’s IAB programs into Technical Programs and 
>> Administrative Support Groups. The aim of this effort is to increase 
>> transparency, visibility, and openness of the architectural work done by the 
>> IAB. A request for feedback about this reorganization has been sent to the 
>> architecture-disc...@iab.org list, see
>> 
>> https://mailarchive.ietf.org/arch/msg/architecture-discuss/mkD3eWYS0ECn44RrABS-gwvrbOY/
>> 
>> The detailed proposal is available on Github:
>> https://github.com/intarchboard/IAB-programs
>> 
>> 
>> If you have comments or concerns you want to discuss, feel free to send me 
>> an email directly, or to the IAB as whole at i...@iab.org!
>> 
>> Best regards,
>> Mirja Kühlewind
>> IAB Chair
>> 
>> On behalf of the IAB
>> 
>> 
> 
> Ole J. Jacobsen
> Editor and Publisher
> The Internet Protocol Journal
> Office: +1 415-550-9433
> Cell:   +1 415-370-4628
> Web: protocoljournal.org
> E-mail: olejacob...@me.com
> E-mail: o...@protocoljournal.org
> Skype: organdemo
> 

___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

IAB report to the community for IETF-109

[IAB Chair]

Dear colleagues,

As also done last time, we have uploaded the full report into the proceedings 
of the datatracker and this email will only summarise a few highlights.

To access the full report, please see here:

https://www.ietf.org/proceedings/108/slides/slides-108-ietf-sessa-iab-report-to-the-community-for-ietf-108-00


IAB Open Meeting
——
The IAB will hold for the second time the IAB Open Meeting. The session will be 
Tuesday, November 17, 14:30 - 15:30 ICT (UTC +7).

This session is aiming to provide an opportunity for more direct interactions 
and technical discussion between the community and the IAB, in both directions: 
providing information about and reporting back on work done, as well as 
gathering input about on-going work.

The agenda is available here:
https://datatracker.ietf.org/meeting/108/materials/agenda-108-iabopen-01


IAB Workshop on COVID-19 Network Impacts
——
The IAB has held a virtual workshop on Network Impacts by the COVID-19 crisis 
this week, Nov 9-13, with in total three sessions on Mon, Wed, Fri. Recording 
are online:

Session 1 - Measurement and Observation: https://youtu.be/RTJNaE7TnGA
Session 2 - Operational Issue: https://youtu.be/tleJg1_SGXM
Session 3 - Future/Conclusions/Parking Lot: https://youtu.be/KCwUBQAkEww

A report is work-in-progress and will be published by the IAB.


IAB Programs
——
The IAB has been working on refactoring its programs. In analysing the current 
IAB programs, the IAB identified two kinds of programs which are quite 
different in their needs and goals. Therefore, the new structure proposes to 
separate today’s IAB programs into Technical Programs and Administrative 
Support Groups. The aim of this effort is to increase transparency, visibility, 
and openness of the architectural work done by the IAB. A request for feedback 
about this reorganization has been sent to the architecture-disc...@iab.org 
list, see

https://mailarchive.ietf.org/arch/msg/architecture-discuss/mkD3eWYS0ECn44RrABS-gwvrbOY/

The detailed proposal is available on Github:
https://github.com/intarchboard/IAB-programs


If you have comments or concerns you want to discuss, feel free to send me an 
email directly, or to the IAB as whole at i...@iab.org!

Best regards,
Mirja Kühlewind
IAB Chair

On behalf of the IAB


___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

IAB report to the community for IETF-108

[IAB Chair]

Dear Colleagues,

Instead of sending the IAB report in full by email, we have this time uploaded 
the report into the proceedings of the datatracker (as also done for other 
reports e.g. from the IESG). We hope that this will help to better archive 
these reports and therefore also make them easier findable later on if needed. 

Here is the link to the full report:

https://www.ietf.org/proceedings/108/slides/slides-108-ietf-sessa-iab-report-to-the-community-for-ietf-108-00


I would still like to take the opportunity and highlight some on-going efforts:


IAB Open Meeting
——
The IAB will hold an IAB Open Meeting during IETF-108 on Tuesday, July 28, in 
Session 2: 13:00-13:50 UTC.

This session is aiming to provide an opportunity for more direct interaction 
and technical discussion between the community and the IAB, in both directions: 
providing information about and reporting back on work done as well as 
gathering input about on-going work. The agenda can be found here:

https://datatracker.ietf.org/meeting/108/materials/agenda-108-iabopen-01


Proposed Program on Evolvabilty, Deployability, and Maintainability (EDM)
——
The scope for this program has been proposed for discussion on the 
architecture-disc...@iab.org list and a new mailing list has been created for 
further discussion at .


IAB Workshop on COVID-19 Network Impacts
——
The IAB is planning to hold a virtual workshop on Network Impacts by the 
COVID-19 crisis in November. A Call for Contributions that will further outline 
the scope and covered list of topics will be send out soon.


If you have comments or concern you want to discuss, feel free to send me an 
email directly or to the IAB as whole at i...@iab.org!

Best regards,
Mirja Kühlewind
IAB Chair

On behalf of the IAB


___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

WG Action: Conclusion of DNS Over HTTPS (doh)

[IAB Chair]

The DNS Over HTTPS (doh) WG in the Applications and Real-Time Area Area 
has concluded. The IESG contact persons are Barry Leiba, Alexey 
Melnikov, and Adam Roach.

The DOH working group was chartered to produce the DoH specification,
which it did some time ago. We have left it open while we sorted out
where other, related work would go, and we now have the ADD working
group chartered to handle some of that. It is, therefore, time to
close the DOH working group.

The mailing list will remain open for now, but might be closed later.
In any case, the archives will stay around.

Thanks very much to Dave Lawrence and Ben Schwartz for having chaired
the DOH working group, and to the participants who helped make it
successful.

___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

IAB Workshop Call for Papers: Design Expectations vs. Deployment Reality

[IAB Chair]

Design Expectations vs. Deployment Reality in Protocol Development


A number of protocols have presumed specific deployment models during 
the development or early elaboration of the protocol.  Actual 
deployments have sometimes run contrary to these early expectations when 
economies of scale, DDoS resilience, market consolidation, or other 
factors have come into play. These factors can result in the deployed 
reality being highly concentrated.



This is a serious issue for the Internet, as concentrated, centralized 
deployment models present risks to user choice, privacy, and future 
protocol evolution.



On occasion, the differences to expectations were almost immediate, but 
they also occur after a significant time has passed from the protocol’s 
initial development.



Examples include:


Email standards, which presumed many providers running in a largely 
uncoordinated fashion, but which has seen both significant market 
consolidation and a need for coordination to defend against spam and 
other attacks. The coordination and centralized defense mechanisms scale 
better for large entities, which has fueled additional consolidation.



The DNS, which presumed deep hierarchies but has often been deployed in 
large, flat zones, leading to the nameservers for those zones becoming 
critical infrastructure. Future developments in DNS may see 
concentration through the use of globally available common resolver 
services, which evolve rapidly and can offer better security. 
Paradoxically, concentration of these queries into few services creates 
new security and privacy concerns.



The Web, which is built on a fundamentally decentralized design, but 
which is now often delivered with the aid of Content Delivery Networks. 
 Their services provide scaling, distribution, and Denial of Service 
prevention in ways that new entrants and smaller systems operators would 
find difficult to replicate.  While truly small services and truly large 
ones may operate using only their own infrastructure, many others are 
left with the only practical choice being the use of a globally 
available commercial service.



Similar developments may happen with future technologies and services. 
For instance, the growing use of Machine Learning technology presents 
challenges for distributing effective implementation of a service 
throughout a pool of many different providers.



In RFC 5218 the IAB tackled what 
made for a successful protocol.  In RFC 8170 
, the IAB described how to handle 
protocol transitions.  This workshop will explore cases where the 
initial system design assumptions turned out to be wrong, looking for 
patterns in what caused those assumptions to fail (e.g., concentration 
due to DDoS resilience) and in how those failures impact the security, 
privacy, and manageability of the resulting deployments.



While the eventual goals might include proposing common remediations for 
specific cases of confounded protocol expectations, the IAB is currently 
inviting papers which:



 *

   Describe specific cases where systems assumptions during protocol
   development were confounded by later deployment conditions.

 *

   Survey a set of cases to identify common factors in these confounded
   expectations.

 *

   Explore remediations which foster user privacy, security and
   provider diversity in the face of these changes.


Important Dates


The workshop will be held June 4-5 in Helsinki, Finland.


Position papers must be submitted by May 3rd at the latest. The program 
committee will review submitted position papers and send an invitation 
to the workshop to one of the paper authors. Invitations will be 
distributed by May 9 at the latest.



Position Paper Requirements


Interested parties must submit a brief document of one to four pages, 
formatted as HTML, PDF, or plain text. We welcome papers that describe 
existing work, answers to the questions listed above, new questions, 
write-ups of deployment experience, lessons-learned from successful or 
failed attempts, and ideally a vision towards taking deployment 
considerations better in account when designing new Internet technology. 
Re-submissions from work presented elsewhere are allowed.



Program Committee


The following persons are IAB contacts for this workshop:


Jari Arkko

Stephen Farrell

Ted Hardie

Christian Huitema

Melinda Shore

Brian Trammell


Position papers should be sent by email to dedr...@iab.org.

Appointment of the RFC Series Editor

[IAB Chair]

The IAB is pleased to announce the re-appointment of Heather Flanagan to 
the position of RFC Series Editor.  The RSOC's recommendation of Heather 
noted her experience, education, skill, and the energy she brings to her 
position; the full IAB is happy to concur.


This appointment is for two years, with options for a further two 
years.  The IAB looks forward to continuing to work with Heather. We 
would also like to thank the RSOC for their work in conducting the 
search and the IAOC for finalizing the contractual details.


regards,

Ted Hardie
for the IAB

ISE appointment

[IAB Chair]

The Internet Architecture Board is pleased to announce the appointment 
of Adrian Farrel as Independent Submission Editor (ISE).  This 
appointment is for a two-year term, beginning on February 15th, 2018.


There was a very strong pool of candidates, and the IAB thanks each of 
the candidates for their willingness to serve.


The candidates each brought forward interesting points about the role 
and its possible evolution, and the IAB hopes to work with Adrian, 
them,  and the wider community on these issues once Adrian has taken up 
the role.


regards,

Ted Hardie
for the IAB

Deadline extended: Call for Participation, Workshop on Internet naming systems

[IAB Chair]

Given the change in date for this workshop, a number of potential 
participants asked if the deadline could be extended.  In order to 
facilitate the broadest possible participation, the IAB has agreed.  
Position papers will now be accepted until August 11, 2017.  The program 
committee will notify accepted participants as soon as possible after 
that, in order to allow for travel arrangements to be made.


A copy of the solicitation and the announcement of the updated dates is 
appended below for your reference.



regards,


Ted Hardie

for the IAB


When the IAB issued the initial call for participation for the 
upcoming ENAME workshop, several folks pointed out conflicts for 
potential attendees on the proposed dates. Among the conflicts were 
meetings of the DNS Operations, Analysis, and Research Center (OARC),  
ISO's technical committee on coded character sets (ISO/IEC JTC1/SC2),  
and the Information-Centric Networking Research Group (ICNRG).  After 
considering these conflicts and others for the times near the original 
dates, the IAB has decided to change the dates to October 10th and 
11th.  Microsoft has kindly offered a venue in Vancouver, British 
Columbia  for these dates.



Note that the new dates immediately follow both Canadian Thanksgiving 
and the U.S. Columbus Day holiday.  While this represents a different 
conflict problem, the IAB has agreed that the overlap with OARC, 
ICNRG, SC2, and the related meetings were serious enough to accept the 
trade-off.  In order to minimize the impact of holiday travel to the 
extent possible, we intend for the workshop to be a half-day on the 
10th and a full day on the 11th.



The updated call for participation is below.


regards,


Ted Hardie

for the IAB




Call for Participation

IAB workshop on Explicit Internet Naming Systems

Internet namespaces relyon Internet connected systems sharing a common 
set of assumptions on the scope, method of resolution, and uniqueness 
of the names.That set of assumption allowed the creation of URIs 
and other systems which presumed that you could authoritatively 
identify a service using an Internet name, a service port, and a set 
of locally-significant path elements.


There are now multiple challenges to maintaining that commonality of 
understanding.


  * Some naming systems wish to use URIs to identify both a service
and the method of resolution used to map the name to a serving
node.  Because there is no common facility for varying the
resolution method in the URI structure, those naming systems must
either mint new URI schemes for each resolution service or infer
the resolution method from a reserved name or pattern.  Both
methods are currently difficult and costly, and the effort thus
scales poorly.
  * Users’ intentions to refer to specific names are now often
expressed in voice input, gestures, and other methods which must
be interpreted before being put into practice.  The systems which
carry on that interpretation often infer which intent a user is
expressing, and thus what name is meant, by contextual elements. 
Those systems are linked to existing systems who have no access to

that context and which may thus return results or create security
expectations for an unintended name.

  * Unicode allows for both combining characters and composed
characters when local language communities have different
practices. When these do not have a single normalization, context
is required to determine which to produce or assume in
resolution.  How can this context be maintained in Internet systems?

While any of these challenges could easily be the topic of a 
stand-alone effort, this workshop seeks to explore whether there is a 
common set of root problems in the explicitness of the resolution 
context, heuristic derivation of intent, or language matching.   If 
so, it seeks to identify promising areas for the development of new, 
more explicit naming systems for the Internet.


We invite position papers on this topic to be submitted by July 28, 
2017 toen...@iab.org .Decisions on accepted 
submissions will be made by August 11, 2017.


Proposed dates for the workshop are October 10th and 11th, 2017 and 
the proposed location is Vancouver, British Columbia.  Further 
logistics will be provided to selected participants.


Ted Hardie

for the IAB

Updated Call for Participation, Workshop on Internet naming systems

[IAB Chair]

When the IAB issued the initial call for participation for the upcoming 
ENAME workshop, several folks pointed out conflicts for potential 
attendees on the proposed dates. Among the conflicts were meetings of 
the DNS Operations, Analysis, and Research Center (OARC),  ISO's 
technical committee on coded character sets (ISO/IEC JTC1/SC2),  and the 
Information-Centric Networking Research Group (ICNRG).  After 
considering these conflicts and others for the times near the original 
dates, the IAB has decided to change the dates to October 10th and 11th. 
Microsoft has kindly offered a venue in Vancouver, British Columbia  for 
these dates.



Note that the new dates immediately follow both Canadian Thanksgiving 
and the U.S. Columbus Day holiday.  While this represents a different 
conflict problem, the IAB has agreed that the overlap with OARC, ICNRG, 
SC2, and the related meetings were serious enough to accept the 
trade-off.  In order to minimize the impact of holiday travel to the 
extent possible, we intend for the workshop to be a half-day on the 10th 
and a full day on the 11th.



The updated call for participation is below.


regards,


Ted Hardie

for the IAB




Call for Participation

IAB workshop on Explicit Internet Naming Systems

Internet namespaces relyon Internet connected systems sharing a common 
set of assumptions on the scope, method of resolution, and uniqueness of 
the names.That set of assumption allowed the creation of URIs and 
other systems which presumed that you could authoritatively identify a 
service using an Internet name, a service port, and a set of 
locally-significant path elements.


There are now multiple challenges to maintaining that commonality of 
understanding.


 * Some naming systems wish to use URIs to identify both a service and
   the method of resolution used to map the name to a serving node. 
   Because there is no common facility for varying the resolution

   method in the URI structure, those naming systems must either mint
   new URI schemes for each resolution service or infer the resolution
   method from a reserved name or pattern.  Both methods are currently
   difficult and costly, and the effort thus scales poorly.
 * Users’ intentions to refer to specific names are now often expressed
   in voice input, gestures, and other methods which must be
   interpreted before being put into practice.  The systems which carry
   on that interpretation often infer which intent a user is
   expressing, and thus what name is meant, by contextual elements. 
   Those systems are linked to existing systems who have no access to

   that context and which may thus return results or create security
   expectations for an unintended name.

 * Unicode allows for both combining characters and composed characters
   when local language communities have different practices. When these
   do not have a single normalization, context is required to determine
   which to produce or assume in resolution.  How can this context be
   maintained in Internet systems?

While any of these challenges could easily be the topic of a stand-alone 
effort, this workshop seeks to explore whether there is a common set of 
root problems in the explicitness of the resolution context, heuristic 
derivation of intent, or language matching.   If so, it seeks to 
identify promising areas for the development of new, more explicit 
naming systems for the Internet.


We invite position papers on this topic to be submitted by July 28, 2017 
toen...@iab.org .Decisions on accepted 
submissions will be made by August 11, 2017.


Proposed dates for the workshop are October 10th and 11th, 2017 and the 
proposed location is Vancouver, British Columbia.  Further logistics 
will be provided to selected participants.


Ted Hardie

for the IAB

IAB report to the community for IETF 99

[IAB Chair]

Dear colleagues,


Continuing the tradition started by Andrew Sullivan, here is the IAB 
report to the community about our activities.  We hope that this 
information allows you to prepare topics you might want to discuss 
during the upcoming open mic time.  Of course, if you have issues you 
want to discuss by email, feel free to send your comments to 
architecture-disc...@iab.org (our public discussion list) or i...@iab.org 
(to reach just the IAB).



The IAB has a few chartered roles. We confirm the appointments to the 
IESG and perform standards process oversight and handle appeals. We also 
perform architectural oversight (including appointing the IRTF Chair), 
we manage the RFC series and the IETF's relationship with IANA, and we 
handle liaisons and appointments both to ISOC and to other 
organizations. We try to ensure that anything we do is part of one of 
these areas of responsibility, and we try to make sure these are all 
covered.



Here's what we've been doing since our last report at IETF 98.  You can 
find mention of each of these on the IAB pages 
athttps://www.iab.org(where there's more background, too).



First, I’m happy to note that there were no appeals during this period. 
 (Appeals and standards process oversight)



In late March, the IAB published a statement on the registration of 
special use names in the ARPA domain 
. 
 This comment focused on the distinction between creating an entry in 
the Special Use Names registry and requesting a delegation within the 
DNS, and it reminded the community that .arpa was an appropriate choice 
for delegations that met the conditions in RFC 3172. (Architecture)



In early May, the IAB provided comments on ICANN’s draft IDN 
implementation guidelines. 
 (Architecture)



In mid-May, the IAB formed a search committee to seek a successor for 
Nevil Brownlee as Independent Series Editor, as documented in RFC 6548. 
 The committee gathered suggestions and comments from the community and 
will be conducting interviews at the Prague IETF. Additional comments 
may be provided to the committee at ise-searc...@iab.org. (RFC Series)



Also in mid-May, the IAB held its annual retreat, including some joint 
time with the IESG.  Among the topics the IAB discussed was the upcoming 
set of work on 5g.  Jari Arkko and Jeff Tantsura have written a blog 
post on 5g 
that 
captures some of the related topics.  The IAB is also a host of a lunch 
meeting on Tuesday of this IETF, where 3GPP colleagues will be available 
to discuss “3GPP & IETF collaboration on 5g”.  Interested folks should 
join us in Congress Hall III or via the remote streams.  Another topic 
from the retreat was a look back at RFC 4084, captured in a blog post on 
the meaning of “Internet Access” 
.  As 
that post notes, we’d be happy for any comments on that topic to be sent 
to architecture-disc...@iab.org 
.(Architecture)



Later in May, the IAB sent a Liaison Statement to the Unicode technical 
committee on the relationship of Unicode Technical Standard #39 to IETF 
work 
. 
 There have since been several informal meetings with Unicode leaders 
on how to encourage increased cooperation between the two groups, and we 
expect to continue to work toward that end over the next year. (Liaisons 
and appointments)



During June, the IAB made three appointments to the Community 
Coordination Group as required by RFC 8090.   Russ Housley and Barry 
Leiba were appointed for two years and  Andrew Sullivan for one year. 
 The IETF representatives then selected Russ as CCG Co-chair, and the 
IAB confirmed him in that post.   We thank each of them for their 
service. (Liaisons and appointments)



A bit later in June, the IAB reappointed Jim Reid to the ICANN Root Zone 
Evolution Review Committee, the appointment being required by RFC 8128. 
 We appreciate Jim’s willingness to serve again.  (Liaisons and 
appointments).



During early July the RSOC program developed  a draft Statement of Work 
for the RFC Series Editor, which will go out for public comment this 
week.  Under the current timeline, the RSOC will make a recommendation 
to the IAB in late September, with the RSE term to begin January 1, 2018 
(RFC Series)



   DOCUMENTS


You can always find the documents the IAB has adopted and is working

on athttps://datatracker.ietf.org/stream/iab.


RFCs published since the last report are:


Coordinating Attack Response at Internet Scale (CARIS) Workshop Report 

Appointment of Russ Housley as CCG co-chair

[IAB Chair]

In accordance with the procedures laid out in RFC 8090, Section 5, the 
Protocol Parameters representatives to the Community Coordination Group 
(CCG) have selected Russ Housley as a co-Chair of the CCG.  As required 
by the RFC, this selection was forwarded to the IAB for confirmation.  
The IAB confirmed the selection at its meeting yesterday, and we thank 
Russ for his willingness to serve.


Regards,

Ted Hardie
for the IAB

Call for Participation, Workshop on Internet naming systems

[IAB Chair]

Call for Participation

IAB workshop on Explicit Internet Naming Systems

Internet namespaces relyon Internet connected systems sharing a common 
set of assumptions on the scope, method of resolution, and uniqueness of 
the names.That set of assumption allowed the creation of URIs and 
other systems which presumed that you could authoritatively identify a 
service using an Internet name, a service port, and a set of 
locally-significant path elements.


There are now multiple challenges to maintaining that commonality of 
understanding.


 * Some naming systems wish to use URIs to identify both a service and
   the method of resolution used to map the name to a serving node.
 Because there is no common facility for varying the resolution
   method in the URI structure, those naming systems must either mint
   new URI schemes for each resolution service or infer the resolution
   method from a reserved name or pattern.  Both methods are currently
   difficult and costly, and the effort thus scales poorly.
 * Users’ intentions to refer to specific names are now often expressed
   in voice input, gestures, and other methods which must be
   interpreted before being put into practice.  The systems which carry
   on that interpretation often infer which intent a user is
   expressing, and thus what name is meant, by contextual elements.
 Those systems are linked to existing systems who have no access to
   that context and which may thus return results or create security
   expectations for an unintended name.

 * Unicode allows for both combining characters and composed characters
   when local language communities have different practices.  When
   these do not have a single normalization, context is required to
   determine which to produce or assume in resolution.  How can this
   context be maintained in Internet systems?

While any of these challenges could easily be the topic of a stand-alone 
effort, this workshop seeks to explore whether there is a common set of 
root problems in the explicitness of the resolution context, heuristic 
derivation of intent, or language matching. If so, it seeks to identify 
promising areas for the development of new, more explicit naming systems 
for the Internet.


We invite position papers on this topic to be submitted by July 28, 2017 
toen...@iab.org .Decisions on accepted 
submissions will be made by August 11, 2017.


Proposed dates for the workshop are September 28th and 29th, 2017 and 
the proposed location is in the Pacific North West of North America. 
 Finalized logistics will be announced prior to the deadline for 
submissions.


Ted Hardie

for the IAB

Appointment to the Internet Society Board of Trustees

[IAB Chair]

As set out in RFC 3677, the IAB is responsible for selecting a certain 
number of the Trustees who serve on the Board of the Internet Society.


In fulfillment of that responsibility, we are happy to announce that 
Sean Turner has been selected for a second three year term, to begin at 
ISOC’s annual general meeting in June.


The IAB had a very strong set of candidates this year, and we would like 
to express our appreciation to each of them for their willingness to 
serve.  We look forward to their continued engagement with the Internet 
Society and the IETF.


Best regards,

Ted Hardie
On behalf of the IAB

Internet Architecture Board statement on the registration of special use names in the ARPA domain

[IAB Chair]

The IAB has noted some controversy in respect of possible registrations 
of names using the mechanisms defined in RFC 6761.

The IAB observes that there is a distinction to be made between creating 
an entry in the Special-Use Domain Names registry where that entry 
prevents the name from being registered in the DNS and creating an entry 
in the Special-Use Domain Names registry where that name is intended to 
be resolved using the DNS protocol.

Through the IAB, the IETF is in a position to specify names beneath the 
top-level domain ARPA, which is designated as the Address and Routing 
Parameter Area domain. This is not a general purpose registry, but it is 
set aside for technical infrastructure established by IETF standards. 
All names registered in the Special-Use Domain Names registry that are 
intended for use via the DNS protocol are found beneath the ARPA top-
level domain.  Other names in the Special-Use Domain Names registry are 
intended for exclusion from DNS resolution. An entry in the Special-Use 
Domain Names Registry that does not require DNS resolution does not 
require the registrant to control the relevant name in the DNS.

In the view of the IAB, when placing any name in the Special-Use Domain 
Names registry with the intention that it be used with the DNS protocol, 
such an entry must be within a domain under the control of the body 
making the registration. For the IETF, an appropriate domain for such 
names would be ARPA, as long as those names meet the conditions in RFC 
3172.

For the IAB,

Ted Hardie
IAB Chair

IAB report to the community before IETF 98

[IAB Chair]

k, for the most part, into programs.  There
are basically two classes: management programs and architectural
programs.  The former are how we handle the oversight of various
things, and the latter are where we do architectural work.  The former
are expected to last as long as the IAB continues to have that
oversight function; the latter last until the IAB has come to a
conclusion on the relevant group of topics, and we expect them to wind
down afterwards.  Programs are listed at
https://www.iab.org/activities/programs/.  As a general rule, each
architectural program has a public mailing list, as well as a
member-specific list.  For subscription instructions, see
https://www.iab.org/iab-mailing-lists/..

We review programs periodically.  In the period since Seoul, we
reviewed the IANA Evolution Program.  The program did a lot of work in
the period prior to the IANA stewardship transition; but with that
event over the IAB determined that we could expect a period of
quiet. Accordingly, the membership of the program has been scaled
back, and the work plan for the program has reverted to the usual
oversight function that was its normal business prior to the
transition work.

The IAB also reviewed the Names and Identifiers Program (INIP).  The
IAB observed that the program had not achieved most of its goals over
its time, and also noted that there did not seem to be the energy and
evidence of progress that might indicate the results would change.
It's worth noting that our discussion of this situation set out a new
presumption for the management of programs.  People have sometimes
made an analogy between programs and IETF working groups, but they
serve different purposes.  Unlike working groups, which have a
procedural function on top of the other functions, IAB programs are
inexpensive to set up and close down.  Therefore, the IAB decided to
close INIP, even though the issues that inspired the program remain
unresolved and even though the IAB continues to think there is a
problem that needs some architectural input.  It appears there are
some other programs that would benefit from similar treatment, and the
IAB will be reviewing those in the near future.

The IAB also reviewed the RFC Series Oversight Committee (RSOC).  This
is an unusual program in that it is formally created by an RFC, but
internally we operate it like any other oversight program.  This
program is functioning well.  The two major work items are any needed
assistance in digesting the format changes, and the RSE RFP and
selection process (which will happen this year).  There was some
discussion of replacing Adam Roach on the RSOC were he to be appointed
as an Area Director, but the IAB decided against it.  There is also a
potentially important thing to draw to community attention: there is a
new guideline for the display of DOIs, and RSOC is unhappy with it.
If the guideline is to be enforced, RSOC plans to recommend
discontinuing the use of DOIs.  More discussion is in the IAB meeting
minutes from 2017-01-11.

We added a new program before IETF 97: the Plenary Planning Program,
to ensure that the IAB component of the IETF plenary is improved.  The
program is fairly new, and this is only the second meeting where its
influence is being felt, so it would be a good time to get feedback
about whether things are getting better.

OPEN COMMUNICATIONS

For some years, the IAB has had a wiki that it uses for its internal
communications.  Because of the role of the IAB, especially in respect
of appointments and outward-facing activities, that wiki has always
been private to the IAB.  Some materials ought to be handled
privately.

Nevertheless, there are lots of things the IAB discusses that do not
need to be private.  Yet the availability of the private wiki
naturally meant that materials tended to end up there even if they did
not need to be private.

To solve this, the IAB has created a separate, public wiki.  It is at
https://www.iab.org/wiki/index.php/Main_Page.  There have been some
teething problems due to accounts not working as expected (and due to
old habits dying hard), but we're working to put any work that does
not need to be private in the public wiki.  

RENEWAL

IAB terms begin and end with the first IETF meeting of the year, so
this report is the final one from this IAB.  The new IAB will begin in
Chicago, at IETF 98:

Alissa Cooper, IETF Chair, Cisco
Brian Trammell, ETH
Erik Nordmark, Independent
Gabriel Montenegro, Microsoft
Jari Arkko, Ericsson
Jeff Tantsura, Futurewei
Joe Hildebrand, Mozilla
Lee Howard, Independent
Mark Nottingham, Akamai Technologies
Martin Thomson, Mozilla
Robert Sparks, Oracle
Suzanne Woolf, Independent
Ted Hardie, Google

We thank outgoing members Ralph Droms, Russ Housley, Andrew Sullivan,
and Dave Thaler for their service.  At IETF 98, the IAB will also
select its new chair and will announce who it is during the course of
the meeting.

Respectfully submitted,

Andrew Sullivan
For the IAB

-- 
IAB Chair (And

Erratum Re: IAB report to the community before IETF 97

[IAB Chair]

Dear colleagues,

My apologies for the error in this report.  There was a placeholder
about the "IETF Trust CCG".  I did not fix it before sending.

As part of the IANA transition, there is some IPR that moves from
ICANN to the IETF Trust.  In order to oversee the use of that IPR,
each operational community appoints three representatives to a
Community Coordination Group that advises the Trust on the use of the
IPR on behalf of the respective community.

In September, the IAB agreed to appoint Alissa Cooper, Ted Hardie, and
Russ Housley to the IANA IPR customer committee.  This is minuted in
our meeting minutes from
https://www.iab.org/documents/minutes/minutes-2016/iab-minutes-2016-09-28/.
I should have sent an announcement about this at the time, but it
appears that I failed to do so.  We regard this as an interim
appointment until we can formalise rules for how we'll undertake these
appointments in the future.

I regret not sending the announcement, and the subsequent error in
this report.

Best regards,

Andrew Sullivan

On Sun, Nov 13, 2016 at 12:26:17AM -0500, IAB Chair wrote:
> Dear colleagues,
> 
> This is the usual IAB report to the community about our activities
> since the previous meeting (in this case, since IETF 96 in Berlin).
> As ever, we hope that this form allows you to prepare topics you might
> want to discuss during the open mic. But of course, if you have views
> you want to make known by email, we're easy to reach: send mail to
> architecture-disc...@iab.org to reach our public discussion list, and
> i...@iab.org to reach just the IAB.
> 
> The IAB has a few chartered roles. We confirm the appointments to the
> IESG and perform standards process oversight and handle appeals. We
> also perform architectural oversight (including appointing the IRTF
> Chair), we manage the RFC series and the IETF's relationship with IANA,
> and we handle liaisons both to ISOC and to other organizations. We try
> to ensure that anything we do is part of one of these areas of
> responsibility, and we try to make sure these are all covered.
> 
> Here's what we've been doing since IETF 96.  You can find mention of
> each of these on the IAB pages at https://www.iab.org (where there's
> more background, too):
> 
> • RFC Format Changes.  You've been hearing for some time about
>   these, and in August the IAB approved the documents to let them
>   take effect.  We'll start to see the changes rolling out into
>   the series soon.  Not all the changes will be visible in every
>   stream right away, but there's reason to believe that the IAB,
>   as the body with oversight of the series, will adopt some of the
>   new features early. (RFC Series)
> 
> • New IRTF Chair.  We appointed Allison Mankin as the new IRTF
>   chair, to replace the departing Lars Eggert.  We appreciate
>   Lars's years of service and Allison's willingness to take on
>   this role.  We also appreciate the other skilled volunteers who
>   made our selection so difficult.  Allison's term actually begins
>   in March, but the early appointment allows an overlap with the
>   end of Lars's term so that the change is smooth.  (architectural
>   oversight, IRTF chair)
> 
> • Appointment to RZERC.  The IANA transition created a Root Zone
>   Evolution Review Committee.  We appointed Jim Reid to it.  We
>   thank him for his service and the other volunteers for being
>   willing to serve. (IANA, external liaisons)
> 
> • Appointment to ICANN Nomcom.  We re-appointed Tim Wicinski to
>   the ICANN Nomcom.  We have heard from previous appointees that
>   there is a significant advantage to re-appointment to this
>   position, so we thank Tim for being willing to take this
>   appointment on again.
> 
> • Appointment to ICANN Technical Liaison Group.  ICANN maintains a
>   group that advises the Board on technical matters pertinent to
>   ICANN's activities.  We re-appointed Paul Wouters to this
>   position. In the aftermath of the IANA transition, there may be
>   some demand for advice from the TLG, so we appreciate Paul's
>   willingness to stand again.
> 
> • IAOC appointment selection in process.  In alternate years, the
>   IAB appoints one IAOC member for a two-year term.  The appointee
>   is also as a consequence a Trustee of the IETF Trust.  The IAB
>   is soliciting comments on the candidates, until 30 November.
>   See the call for feedback at
>   
> https://www.iab.org/2016/11/03/please-comment-on-iaoc-candidates-for-iab-selection/.
> 
> • [IETF Trust CCG appointments -- hold place here]
> 
> • Statement about the IANA stewardship transition.  The IAB put
>   out one fi

IAB report to the community before IETF 97

[IAB Chair]

 Review Committee Appointment
Procedures

The other documents are related to the IAB's architectural functions:

draft-iab-privsec-confidentiality-mitigations-08
Confidentiality in the Face of Pervasive Surveillance
draft-iab-protocol-transitions-03
Out With the Old and In With the New: Planning for Protocol
Transitions
draft-iab-web-pki-problems-05
Improving the Public Key Infrastructure (PKI) for the World Wide
Web

Two of these come from the IAB Privacy and Security program.

PROGRAMS

The IAB organizes its work, for the most part, into programs.  There
are basically two classes: management programs and architectural
programs.  The former are how we handle the oversight of various
things, and the latter are where we do architectural work.  The former
are expected to last as long as the IAB continues to have that
oversight function; the latter last until the IAB has come to a
conclusion on the relevant group of topics, and we expect them to wind
down afterwards.  Programs are listed at
https://www.iab.org/activities/programs/.  In general, programs and
their mailing lists are closed to members.  But also as a general
rule, there is a public list associated with architectural programs
that is public.  For subscription instructions, see
https://www.iab.org/iab-mailing-lists/.  

We review programs periodically.  If you've read previous reports, you
will know that we had a very aggressive period of reviewing everything
to ensure we were up to date.  Now that that's complete, we have
reduced the frequency but are still reviewing architectural programs
so that they are examined more often than annually.  The Privacy and
Security Program has the two documents mentioned above, and is also
deciding what to do with draft-hardie-privsec-metadata-insertion.  The
program will also meet this week to discuss whether it needs to be
re-scoped (or perhaps whether it is finished) once these documents are
done.

We added a new program since IETF 96: the Plenary Planning Program, to
ensure that the IAB component of the IETF plenary is improved.
It will meet during IETF 97, as will the Internationalization Program,
the Names and Identifiers Program, the Stack Evolution Program, and
the RSOC.

During the time leading up to the IANA stewardship transition, it
became clear that a body had come into existence that was originally
supposed to be informal: IPROC (IETF Protocol Registries Oversight
Committee).  To tidy things up, the IAB created a program that was
also a subcommittee of the IAOC and that would serve this role.  Now
that the new Supplemental Agreement is in place between the IETF and
ICANN, this formalism is no longer needed.  In keeping with the
principle, "Just enough formality to get things done," we expect to
wind this program down as soon as the IAB and IAOC can co-ordinate
it.

A RETURN TO ARCHITECTURE

Finally, we can report the happy news that the IANA stewardship
transition did happen as scheduled on 1 October 2016.  There was some
turbulence in that plan in the period since IETF 96, but in the end it
worked out.  This means that the IAB can spend less time on
administrative issues like IANA and return some of its attention to
the architectural issues facing the Internet.  We hope that the
plenary discussion at IETF 97 is a good way to mark that turn of
attention.

Respectfully submitted,

Andrew Sullivan
For the IAB

-- 
IAB Chair (Andrew Sullivan)
iab-ch...@iab.org

IAB Statement on IPv6

[IAB Chair]

Dear colleagues,

The IAB has posted a statement to its website about IPv6
(https://www.iab.org/2016/11/07/iab-statement-on-ipv6/).  It is
reproduced in full below:

The Internet Architecture Board (IAB), following discussions in the
Internet Engineering Task Force (IETF), advises its partner Standards
Development Organizations (SDOs) and organizations that the pool of
unassigned IPv4 addresses has been exhausted, and as a result we are
seeing an increase in both dual-stack (that is, both IPv4 and IPv6)
and IPv6-only deployments, a trend that will only
accelerate. Therefore, networking standards need to fully support
IPv6. The IETF as well as other SDOs need to ensure that their
standards do not assume IPv4.

The IAB expects that the IETF will stop requiring IPv4 compatibility
in new or extended protocols. Future IETF protocol work will then
optimize for and depend on IPv6.

Preparation for this transition requires ensuring that many different
environments are capable of operating completely on IPv6 without being
dependent on IPv4 [see RFC 6540].  We recommend that all networking
standards assume the use of IPv6, and be written so they do not
require IPv4. We recommend that existing standards be reviewed to
ensure they will work with IPv6, and use IPv6 examples. Backward
connectivity to IPv4, via dual-stack or a transition technology, will
be needed for some time. The key issue for SDOs is to remove any
obstacles in their standards which prevent or slow down the transition
in different environments.

In addition, the IETF has found it useful to add IPv6 to its external
resources (e.g., Web, mail) and to also run IPv6 on its conference
network since this helps our participants and contributors and also
sends the message that we are serious about IPv6. That approach might
be applicable to other SDOs.

We encourage the industry to develop strategies for IPv6-only
operation. We welcome reports of where gaps in standards remain,
requiring further developments in IPv6 or other protocols. We are also
ready to provide support or assistance in bridging those gaps.

Best regards,

Andrew Sullivan
for the IAB

-- 
IAB Chair (Andrew Sullivan)
iab-ch...@iab.org

Report from the IAB

[IAB Chair]

nough that we were unable to recover.  We have a
"hopper" of excellent plenary topics (which we think need to be
informative or entertaining -- preferably both -- to the general IETF
audience), but practical arrangements were hard to make this time.
We're going to address this by starting earlier from now on.  We've
already begun organizing things for IETF 97, so we won't be
disappointed again.  We apologize for missing our goal for IETF 96.

Respectfully submitted,
Andrew Sullivan
for the IAB

-- 
IAB Chair (Andrew Sullivan)
iab-ch...@iab.org

Testimony to US Commerce Committee

[IAB Chair]

Dear colleagues,

Today I was invited to appear before the United States Senate
Committee on Commerce, Science, and Transportation at the hearing on
“Examining the Multistakeholder Plan for Transitioning the Internet
Assigned Number Authority.”  I spoke in my role as IAB Chair.  Still,
I should emphasise that my remarks are not a consensus position of the
IAB, so if you think I said something boneheaded, blame me and not the
IAB as a whole.

My submitted tesimony is available on the IAB site at
<https://www.iab.org/2016/05/24/iab-chair-testifies-before-u-s-senate-at-iana-transition-hearing/>.

Video of the hearing is archived at
<http://www.commerce.senate.gov/public/index.cfm/hearings?ID=418B1D81-1F0B-4E09-BB71-A98FBABE42B9>

The transition of IANA stewardship is still proceeding.  If you want
to follow more, I suggest discussing it on the IANAPLAN WG list, 
ianap...@ietf.org.

Best regards,

Andrew

-- 
IAB Chair (Andrew Sullivan)
iab-ch...@iab.org

IAB sent comments on ICANN draft bylaws

[IAB Chair]

Dear colleagues,

The IAB sent a response to ICANN in response to their call for
comments on their proposed new bylaws.  The IAB announcement is at
https://www.iab.org/2016/05/04/iab-comments-on-draft-new-icann-bylaws/
and you can see the posting in the ICANN forum at
http://forum.icann.org/lists/comments-draft-new-bylaws-21apr16/msg1.html.

Best regards,

Andrew
(for the IAB)

-- 
IAB Chair (Andrew Sullivan)
iab-ch...@iab.org

Report from the IAB before IETF 95

[IAB Chair]

up next), but it has been generating quite a
bit of discussion on inip-disc...@iab.org.  The arcing BoF
at IETF 95 was inspired in part by some of those discussions.  

Privacy and Security

Reviewed 2016-01-13.

INTERNET RESEARCH TASK FORCE

The IAB appoints the IRTF Chair. Lars Eggert, the current IRTF Chair,
has announced that he will not seek re-appointment, having served
since March of 2011. The IAB is starting its search for a new Chair.
We are grateful for Lars's tremendous service in this role, and we'll
have our work cut out for us. We will be making announcements soon
about our search, so look for those. In the meantime, if you are
interested or know someone who you think might be a good candidate,
have a look at RFC 7827 to see what the job entails.

Respectfully submitted,
Andrew Sullivan
For the IAB


-- 
IAB Chair (Andrew Sullivan)
iab-ch...@iab.org

IAB sent comments to the ICANN CCWG-Accountability

[IAB Chair]

Dear colleagues,

The IAB sent comments to the ICANN Cross Community Working Group on
Enhancing ICANN Accountability (CCWG-Accountability).  The CCWG asked
that comments be submitted as a response to a survey, so we did that.
Our responses and the comments we made can be found at 
<https://www.iab.org/documents/correspondence-reports-documents/2015-2/iab-comments-on-the-ccwg-accountability-3d-draft-report/>.

Best regards,

Andrew (for the IAB)

-- 
IAB Chair (Andrew Sullivan)
iab-ch...@iab.org

IAB appoints Tim Wicinski to ICANN Nomcom

[IAB Chair]

Dear colleagues,

The IAB is pleased to appoint Tim Wicinski to the ICANN Nomcom.  

Tim has been involved with DNS and the standards processes for many years..
In the past several years, he has been co-chair of the DNS Operations (DNSOP)
Working Group within the IETF; and more recently the co-chair of the DNS
Privacy Exchange (DPRIVE) Working Group.  Tim is a Site Reliability Architect
at Salesforce.com, with a focus on DNS and CDN technologies.

The IAB had several able candidates to choose from this year, which made the 
choice difficult.  We thank all the volunteers for putting their names forward, 
and encourage their continued engagement with the IETF.  The IAB also wishes to 
thank John Levine for his previous service as the IAB appointee on the ICANN 
Nomcom.

Best regards,

Andrew Sullivan
IAB chair

Call for community comment: draft-iab-xml2rfcv2-01

[IAB Chair]

Dear colleagues,

This is an announcement of an IETF-wide Call for Comment on
draft-iab-xml2rfcv2-01.
 
The document is being considered for publication as an Informational
RFC within the IAB stream, and is available for inspection here:

https://datatracker.ietf.org/doc/draft-iab-xml2rfcv2/?include_text=1
 
Please note that the purpose of the document is to represent the state
of the vocabulary as actually implemented in the xml2rfc system as of
current writing.  Therefore, if you have particular concerns about the
design or functionality described in this I-D, the comments about
those issues are best addressed to the authors of another draft
(draft-hoffman-xml2rfc-21).  Discussion of that draft is active on the
rfc-inter...@rfc-editor.org mailing list.  We ask that comments about
this draft focus on the degree to which it accurately reflects the
current xml2rfc implementation, and whether it is clear,
comprehensible, useful, and complete.

The Call for Comment will last until 2015-09-02. Please send comments
to i...@iab.org.  The RFC Editor has also asked that
rfc-inter...@rfc-editor.org be copied. 

Best regards,

Andrew Sullivan
On behalf of the IAB

Request for volunteers or nominations to 2016 ICANN NomCom

[IAB Chair]

Dear Colleagues:

The IAB (on behalf of the IETF) has been asked to supply a member to the 2016 
ICANN
Nominating Committee (NomCom). The IAB would therefore like to ask the 
community 
for volunteers to serve on the ICANN NomCom. Last year, John Levine did the
job for the IETF community, and he is willing to serve again. The IAB would 
like to see
whether others are interested in serving in this capacity.

If you are interested in serving on the ICANN NomCom, please send a short 
e-mail to 
iab-chair at iab.org and execd at iab.org with your motivation and information 
concerning 
your familiarity with the IETF and ICANN. Alternatively, if you know of someone 
who may 
be a good fit for this position, please send the name and email address to 
e-mail to
iab-chair at iab.org and execd at iab.org. The deadline for nominations or 
volunteers is 
28 August 2015.

After asking for community input on the candidates, the IAB will select from 
the available 
candidates. We shall take into account canidates' familiarity with ICANN and 
the IETF 
(including their roles and processes). The selected candidate will serve on the 
ICANN 
NomCom on personal title;  however, we will be looking for a candidate who has 
an 
understanding of the interests of the IETF and the broader technical community.

The ICANN NomCom process itself is governed by the ICANN bylaws; an abstract of 
the relevant 
articles can be found at http://nomcom.icann.org/bylaws.htm.  In addition, each 
NomCom 
determines a number of its own operational procedures, including the role of 
the NomCom in 
recruiting and selecting candidates for ICANN leadership positions.  Based on 
the experience
of previous volunteers, the time commitment is significant.  The selected 
person should be
prepared to participate in the recruitment of potential candidates for ICANN 
leadership
positions (a few hours per month November through April); a few hours on 
conference calls
each month (and even more near selection); ten or more hours per month 
reviewing and
assessing candidate qualifications in April, May, and June; and multiple days 
of face-to-face
meetings of the full NomCom at each of the three ICANN meetings.

The ICANN NomCom typically meets in person at or around three consecutive ICANN 
meetings
in various locations throughout the world, resulting next summer in a final 
slate of candidates 
for the ICANN Board, the GNSO, ccNSO, and ALAC.

NOTE: ICANN covers travel and hotel costs for a pre-determined number of days 
at each
of the 3 consecutive ICANN meetings under prevailing ICANN policies.

Candidates should be able to join monthly teleconferences (typically at UTC 
14:00), with the 
expectation that these teleconferences will held weekly during the candidate 
assessment 
process in May and June.

For more information about the ICANN NomCom see: http://nomcom.icann.org/

On behalf of the IAB,
  Andrew Sullivan
  IAB Chair

IAB Re-Appoints Jonne Soininen as Liaison to the ICANN Board

[IAB Chair]

Dear colleagues,

The IAB has been deliberating the selection of the liaison from the IETF 
community to ICANN Board over the past several weeks. After seeking feedback 
from the IETF community, the IAB has decided to re-appoint Jonne Soininen to 
this position. 

The IAB extends our sincere thanks to Jonne for serving the community in this 
role. 

On behalf of the IAB, 
Andrew Sullivan 
IAB Chair

Call for comment: draft-iab-doi-04.txt (Assigning Digital Object Identifiers to RFCs)

[IAB Chair]

Dear colleagues,

This is an announcement of an IETF-wide Call for Comment on
draft-iab-doi-04.

The document is being considered for publication as an Informational RFC
within the IAB stream, and is available for inspection here:
http://datatracker.ietf.org/doc/draft-iab-doi/

The Call for Comment will last until 2015-07-29. Please send comments to
i...@iab.org.

Best regards,
Andrew Sullivan
IAB chair
On behalf of the IAB

IAB Statement on the Trade in Security Technologies

[IAB Chair]

Dear colleagues,

I thought it might be of interest to draw your attention to the IAB's statement 
on the trade in security technologies.  You can find it on the IAB website, at 
https://www.iab.org/documents/correspondence-reports-documents/2015-2/iab-statement-on-the-trade-in-security-technologies/.
  

Best regards,

Andrew Sullivan
IAB chair

Appointment of Daniel Migault as IETF Liaison to ICANN Root Server System Advisory Council (RSSAC)

[IAB Chair]

The IAB is pleased to announce the appointment of Daniel Migault as the 
IETF liaison to the ICANN Root Server System Advisory Council (RSSAC).

The IAB thanks all those who volunteered to serve, and thanks Daniel for 
taking on the task.


On Apr 13, 2015, at 10:42 AM, IAB Chair wrote:

 The IAB is responsible for appointing a liaison manager to the ICANN
 Root Server System Advisory Committee (RSSAC) [1][2].
 
 We are currently soliciting volunteers for this position. Nominations
 (including self-nominations) for this position should be sent to iab-
 chair at iab.org and execd at iab.org no later than Friday, 8 May
 2015.
 
 The current temporary liaison is Marc Blanchet, who was appointed in
 his role as IAB member during the restructuring process of RSSAC.
 
 The person filling the role of liaison manager needs to have 
 familiarity with the IETF and ICANN processes, have expertise in the 
 DNS, and be involved in the related IETF working groups.
 
 The liaison sits on the RSSAC committee as a non-voting member and
 follows RSSAC procedures. The liaison acts a conduit between the two
 organizations on matters that need to be coordinated or communicated
 between the two organizations.
 
 It is expected that the liaison manager attends IETF and ICANN 
 meetings, and more specifically the RSSAC meetings. The liaison role 
 is non-voting. Expertise in security and internationalization would be 
 a plus.
 
 The IETF liaison process is defined in RFCs 4052, 4053, and 4691.
 
 Please forward this message to any interested party.
 
 Best regards,
 Andrew Sullivan
 IAB Chair
 
 [1] http://www.icann.org/en/groups/rssac
 [2] https://www.iab.org/documents/correspondence-reports-documents/
 2015-2/iab-liaison-to-icann-root-server-system-advisory-council-rssac/

Call for Feedback on the current IETF Liaison to the ICANN Board of Directors

[IAB Chair]

Dear colleagues,

As part of its oversight responsibility for the technical liaison
relationships with other organizations concerned with standards and
other technical and organizational issues relevant to the world-wide
Internet, the IAB is soliciting comments from the community on the
performance of the current IETF Liaison to the ICANN Board of Directors,
Jonne Soininen.  We are interested in comments on what has gone well or
badly in the last several years.  Jonne has been serving in the position
since 2013.

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

We would appreciate receiving comments by 23 June 2015, as the IAB will
likely begin the next steps in the oversight process shortly before
IETF 93 in Prague.

Thank you,
Andrew Sullivan
IAB Chair

Call for comment: draft-iab-semi-report-00.txt

[IAB Chair]

Dear colleagues,

This is an announcement of an IETF-wide Call for Comment on
draft-iab-semi-report-00.txt.

The document is being considered for publication as an Informational RFC
within the IAB stream, and is available for inspection here:
https://www.ietf.org/id/draft-iab-semi-report-00.txt

The Call for Comment will last until 2015-07-02. Please send comments to
i...@iab.org.

Best regards,
Andrew Sullivan
IAB chair
On behalf of the IAB

Call for comment: draft-iab-strint-report-02.txt

[IAB Chair]

Dear colleagues,

This is an announcement of an IETF-wide Call for Comment on 
draft-iab-strint-report-02.txt.
 
The document is being considered for publication as an Informational RFC 
within the IAB stream, and is available for inspection here: 
https://www.ietf.org/id/draft-iab-strint-report-02.txt
 
The Call for Comment will last until 2015-07-01. Please send comments to 
i...@iab.org.

Best regards,
Andrew Sullivan
IAB chair
On behalf of the IAB

Call for community feedback for RSSAC liaison appointments

[IAB Chair]

Dear Colleagues,

The IAB recently requested nominations for a liaison manager to the 
ICANN Root Server System Advisory Committee (RSSAC) [1]. We have a 
number of candidates, and are now soliciting comment from the community 
on these candidates:

- Al Bolivar 
- Shane Kerr 
- Warren Kumari 
- Daniel Migault 
- Tomofumi Okubo

Please send your remarks in confidence about any or all candidates to
iab-ch...@iab.org and ex...@iab.org by 27 May 2015.  We thank you in 
advance for your help. 

Kind regards,

Andrew Sullivan
IAB Chair

[1] 
https://www.iab.org/2015/04/13/call-for-nominations-for-ietf-liaison-to-icann-rssac/

Remarks from the I* meeting

[IAB Chair]

Hi,

I posted some remarks about participation in the recent “I*” meeting.  The 
posting is at https://www.iab.org/2015/05/07/update-from-i-meeting/.

Best regards,

Andrew Sullivan
IAB Chair

Call for nominations for IETF liaison to ICANN RSSAC

[IAB Chair]

The IAB is responsible for appointing a liaison manager to the ICANN
Root Server System Advisory Committee (RSSAC) [1][2].

We are currently soliciting volunteers for this position. Nominations
(including self-nominations) for this position should be sent to iab-
chair at iab.org and execd at iab.org no later than Friday, 8 May
2015.

The current temporary liaison is Marc Blanchet, who was appointed in
his role as IAB member during the restructuring process of RSSAC.

The person filling the role of liaison manager needs to have familiarity
with the IETF and ICANN processes, have expertise in the DNS, and be
involved in the related IETF working groups.

The liaison sits on the RSSAC committee as a non-voting member and
follows RSSAC procedures. The liaison acts a conduit between the two
organizations on matters that need to be coordinated or communicated
between the two organizations.

It is expected that the liaison manager attends IETF and ICANN meetings,
and more specifically the RSSAC meetings. The liaison role is non-
voting. Expertise in security and internationalization would be a plus.

The IETF liaison process is defined in RFCs 4052, 4053, and 4691.

Please forward this message to any interested party.

Best regards,
Andrew Sullivan
IAB Chair

[1] http://www.icann.org/en/groups/rssac
[2]
https://www.iab.org/documents/correspondence-reports-documents/2015-2/iab-liaison-
to-icann-root-server-system-advisory-council-rssac/

Call for Review of draft-iab-privsec-confidentiality-threat-04, Confidentiality in the Face of Pervasive Surveillance: A Threat Model and Problem Statement

[IAB Chair]

Dear colleagues,

This is a call for review of Confidentiality in the Face of Pervasive 
Surveillance: A Threat Model and Problem Statement prior to potential approval 
as an IAB stream RFC.

The document is available for inspection here:

http://www.ietf.org/id/draft-iab-privsec-confidentiality-threat-04.txt 
http://www.ietf.org/id/draft-iab-privsec-confidentiality-threat-04.txt

The Call for Review will last until 22 April 2015.  Please send comments to 
i...@iab.org.

On behalf of the IAB,
  Andrew Sullivan 
  IAB Chair

Call for Papers: IAB/ISOC Workshop on Coordinating Attack Response at Internet Scale

[IAB Chair]

Internet Architecture Board (IAB) and Internet Society (ISOC) workshop on
Coordinating Attack Response at Internet Scale (CARIS)

June 19, 2015, Intercontinental Hotel in Berlin, hosted by the 27th annual 
FIRST Conference

Workshop Information: https://www.iab.org/activities/workshops/caris/ 

Numerous incident response efforts exist to mitigate the effects of attacks.  
Some are  operator driven focused on specific attack types, while others are 
closed analysis and sharing groups spanning many attack types.  Many of the 
operator driven models work with members to mitigate the effects of such 
attacks for all users, but how to contribute information to these efforts is 
not always known or easy to discover.  Sharing within closed community analysis 
centers is only practical for very large organizations as a result of resource 
requirements even to be able to use shared data.  Without coordination, these 
efforts are not only duplicated, but leave out protections for small and medium 
sized organizations.  These organizations may be part of the supply chain for 
larger organizations, a common pathway for successful attacks.

This workshop aims to bring together operators, researchers, CSIRT team 
members, service providers, vendors, information sharing and analysis center 
members to discuss approaches to coordinate attack response at Internet scale. 

The day-long workshop will include a mix of invited and selected speakers with 
opportunities to collaborate throughout, taking full advantage of the 
tremendous value of having these diverse communities with common goals in one 
room.


Submission Instructions:
Attendance at the workshop is by invitation only. There is no fee to attend the 
workshop.

For existing attack-mitigation working groups, the survey at

https://internetsociety2.wufoo.com/forms/caris-workshop-organisation-template/ 
should be completed by those organizations whose mitigation efforts or use case 
analyses apply. The data gathered through this questionnaire, including how to 
participate or contribute to your attack mitigation working group, will be 
shared with all of the participants at the workshop to better enable 
collaboration with your effort. 

Alternatively, submit a 2-page research paper that includes some key insight or 
challenge relevant to the broader group.  This may include research topics 
around attack mitigation or information sharing/exchange, success stories from 
your CSIRT, lessons learned, or a deep dive on a particular topic such as 
privacy or trust.

Submissions accepted at: https://easychair.org/conferences/?conf=caris2015
Final Submission Deadline: 3 April 2015
Notification Deadline: 1 May 2015
Workshop Date: 19 June 2015

All attendees are required to complete the survey or submit a 2-page research 
paper to the CARIS program committee via EasyChair.  Accepted submissions will 
be published on the IAB website at: 
https://www.iab.org/activities/workshops/caris/ 

Attendees will be selected based on these submissions to ensure the workshop 
will be beneficial to all and has the potential to impact the coordination of 
attack response at Internet scale.

Sponsored by the Internet Architecture Board and the Internet Society.
http://www.iab.org/
http://www.internetsociety.org/

IAB statement on Liaison Compensation

[IAB Chair]

Please find this statement issued by the IAB today.

On behalf of the IAB,
Russ Housley
IAB Chair

= = = = = = = = = = = = =

IAB statement on Liaison Compensation

Under its responsibilities documented in RFC 2850 the IAB will, from time to 
time, appoint people to represent the IETF or IAB to other organizations as 
liaisons. The procedures for how liaison relations are handled are currently 
documented in RFCs 4052, 4053, and 4691. In addition, the IAB responsibilities 
include appointments to various other bodies, such as ISOC Board Trustees and 
ICANN board liaisons, as well as committee members for the ICANN TLG and ICANN 
NomCom.

While the roles differ, the IAB generally believes that the guiding principle 
should be that individuals serve without expectation of direct compensation 
from the bodies to which they are appointed, so as to avoid any appearance of 
conflict of interest. As a result, apart from reasonable travel expenses, the 
IAB generally requests that its appointees decline offers of compensation from 
the bodies to which they are appointed. The IAB will consider exceptions on a 
case-by-case basis.

IAB liaison to ICANN Root Server System Advisory Council (RSSAC)

[IAB Chair]

Historically, the Internet Architecture Board (IAB) has provided a
liaison to the Root Server System Advisory Council (RSSAC). With the
recent reestablishment of the RSSAC, this statement confirms this
on-going liaison.

This liaison is nominated by IAB using its own procedures, as
described in RFC2850. The IAB-appointed liaison sits on the RSSAC
committee as a non-voting member and follows RSSAC procedures. The
liaison acts a conduit between the two organisations on matters that
need to be coordinated or communicated between the two organisations.

Russ Housley
Chair of Internet Architecture Board (IAB)

Lars-Johan Liman
Co-chair of Root Server System Advisory Council (RSSAC)

Tripti Sinha
Co-chair of Root Server System Advisory Council (RSSAC)

Appointment to the ICANN Technical Liaison Group

[IAB Chair]

Dear Colleagues,

The IAB has selected Paul Wouters to serve a two-year term on the ICANN 
Technical Liaison Group (TLG).

The IAB thanks all of the candidates.  This was a difficult decision 
with two strong candidates.

The IAB thanks Daniel Migault for his service on the ICANN TLG during 2014.

On behalf of the IAB,
  Russ Housley
  IAB Chair

Call for Review of draft-iab-iana-principles-01, Principles for Operation of Internet Assigned Numbers Authority (IANA) Registries

[IAB Chair]

This is a call for review of Principles for Operation of Internet Assigned 
Numbers Authority (IANA) Registries prior to potential approval as an IAB 
stream RFC.

The document is available for inspection here:
http://www.ietf.org/id/draft-iab-iana-principles-01.txt

The Call for Review will last until 5 January 2015.  Please send comments to 
i...@iab.org. 

On behalf of the IAB,
  Russ Housley
  IAB Chair

IAB statement on the NETmundial Initiative

[IAB Chair]

Please find this statement issued by the IAB today.

On behalf of the IAB,
 Russ Housley
 IAB Chair

= = = = = = = = = = = = =

IAB statement on the NETmundial Initiative

The IAB thinks it is valuable to develop tools to support communities
that can share solutions, expertise, and research related to Internet
Governance.  We welcomed the initial NETmundial meeting as an additional
way to foster the development of a broadly based community engaged in
supporting the Internet's distributed systems and methods.  We believe
that the recent NETmundial Initiative
(https://www.netmundial.org/press-release-1) to develop a long-running
dialogue on these topics, in the form of a web site and collection of
materials, may be a valuable addition to the overall community efforts.

We are concerned, however, that the creation of a highly structured
coordination council for the Initiative may impede the development of
broad participation, and so may be premature.  Because the coordination
council members appear to be the responsible parties for the effort, the
effort may not foster the sort of community engagement that we believe is
fundamental to the Internet's distributed nature and the NETmundial
principles (https://www.netmundial.org/principles).

To make the Internet work, many people with unique perspectives of the
Internet and from different communities must cooperate.  We believe a
broadly based dialogue among all these communities is necessary, and
support any effort to enable this dialogue.  The permissionless
innovation given as the goal of this effort is better served by first
enabling technical infrastructure to further that cooperation; that
might require some lightweight administration driven by community
consensus.  No coordination council is needed now, and therefore the IAB
will not participate in the council at this time.

IAOC Selection Announcement

[IAB Chair]

The IAB is responsible for selecting one IETF Administrative Oversight 
Committee (IAOC) member for a two-year term starting in March 2015.  The 
selection was made in accordance with BCP 101 and BCP 113.

A call for nominations was issued on 8 October 2014. Nominations for four 
candidates were received, and three of them were willing to serve.  All who
accepted the nomination were very strong candidates and their names were 
announced on 7 November 2014.

After obtaining written input from all nominees and feedback from the 
community on all of them, the IAB discussed which candidate to choose.  
After significant discussion, the IAB decided to appoint Benson Schliesser
to this position.

The IAB thanks all of the nominees for their willingness to serve the
IETF community.  

On Behalf of the IAB,
  Russ Housley
  IAB Chair

Please comment on ICANN TLG Candidates

[IAB Chair]

Dear Colleagues,

The IAB recently requested nominations to the ICANN Technical
Liaison Group (TLG).  We have a number of candidates, and we
are soliciting comment from the community on these candidates.

The following candidates have put their names forward:

   Loa Andersson 
   Paul Wouters

Please send your remarks in confidence about any or all candidates to
iab-ch...@iab.org and ex...@iab.org.  We thank you in advance for
your help.

Best regards,
  Russ Housley
  IAB Chair

Please comment on IAOC candidates for IAB selection

[IAB Chair]

As described in BCP 101 (RFC 4071) and BCP 113 (RFC 4333),
the IESG and the IAB each select one person for a two-year IAOC
term in alternate years. This year, the IAB will select one person
for a term beginning in March 2015. 

Following the call for nominations, which ran from 8 October 2014 
through 5 November 2014, the IAB contacted each person that
was nominated, asking them to accept or reject their nomination.  At 
this point, 3 people have indicated a willingness to serve. They are:

   Hago Dafalla
   Adrian Farrel
   Benson Schliesser

The IAB is actively soliciting confidential comments on these people
and their ability to serve on the IAOC. The IAB needs to receive these
comments by 28 November 2014 in order to make a selection in early
December 2014. Please send comments to iab-ch...@iab.org and
ex...@iab.org.

Note that the NomCom will also be selecting a person to serve on the 
IAOC for a two-year term. This process is orthogonal, the IAB is not 
privy to comments you might have submitted to the NomCom.
 
On Behalf of the IAB,
   Russ Housley
   IAB Chair

IAB Statement on Internet Confidentiality

[IAB Chair]

Please find this statement issued by the IAB today.

On behalf of the IAB,
  Russ Housley
  IAB Chair

= = = = = = = = = = = = =

IAB Statement on Internet Confidentiality

In 1996, the IAB and IESG recognized that the growth of the Internet
depended on users having confidence that the network would protect
their private information.  RFC 1984 documented this need.  Since that
time, we have seen evidence that the capabilities and activities of
attackers are greater and more pervasive than previously known.  The IAB
now believes it is important for protocol designers, developers, and
operators to make encryption the norm for Internet traffic.  Encryption
should be authenticated where possible, but even protocols providing
confidentiality without authentication are useful in the face of
pervasive surveillance as described in RFC 7258.

Newly designed protocols should prefer encryption to cleartext operation.
There may be exceptions to this default, but it is important to recognize
that protocols do not operate in isolation.  Information leaked by one
protocol can be made part of a more substantial body of information
by cross-correlation of traffic observation.  There are protocols which
may as a result require encryption on the Internet even when it would
not be a requirement for that protocol operating in isolation.

We recommend that encryption be deployed throughout the protocol stack
since there is not a single place within the stack where all kinds of
communication can be protected.

The IAB urges protocol designers to design for confidential operation by
default.  We strongly encourage developers to include encryption in their
implementations, and to make them encrypted by default.  We similarly
encourage network and service operators to deploy encryption where it is
not yet deployed, and we urge firewall policy administrators to permit
encrypted traffic.

We believe that each of these changes will help restore the trust users
must have in the Internet.  We acknowledge that this will take time and
trouble, though we believe recent successes in content delivery networks,
messaging, and Internet application deployments demonstrate the
feasibility of this migration.  We also acknowledge that many network
operations activities today, from traffic management and intrusion
detection to spam prevention and policy enforcement, assume access to
cleartext payload.  For many of these activities there are no solutions
yet, but the IAB will work with those affected to foster development of
new approaches for these activities which allow us to move to an Internet
where traffic is confidential by default.

Reappointment of Lars Eggert as IRTF Chair

[IAB Chair]

The Internet Architecture Board is pleased to announce the reappointment of
Lars Eggert as the Internet Research Task Force (IRTF) Chair. The IAB received
a significant number of comments saying that Lars is doing a excellent job.
This appointment is for a two year term, beginning in March 2015 and
ending in March 2017.

On behalf of the IAB,
  Russ Housley
  IAB Chair

Re: Call for Papers: IAB Workshop on Stack Evolution in a Middlebox Internet (SEMI)

[IAB Chair]

As a reminder, the deadline for the IAB workshop on Stack Evolution in a
Middlebox Internet (SEMI) is coming up. Prospective participants are
invited to submit short (i.e., about two pages) position papers outlining
their views on one or more topics related to the scope of the workshop.
Authors and titles for position papers must be registered by Friday,
31 October 2014, but the deadline for complete position papers has been
extended by a week to Friday, 7 November 2014.

On behalf of the IAB,
  Russ Housley
  IAB Chair


On Sep 9, 2014, at 12:09 PM, IAB Chair wrote:

 IAB Workshop on Stack Evolution in a Middlebox Internet (SEMI)
 26-27 January 2015 – ETH Zürich, Switzerland
 
 The Internet’s transport layer has ossified, squeezed between narrow 
 interfaces (from BSD sockets to pseudo-transport over HTTPS) and 
 increasing in-network modification of traffic by middleboxes that make 
 assumptions about the protocols running through them. This ossification 
 makes it difficult to innovate in the transport layer, through the 
 deployment of new protocols or the extension of existing ones. At the 
 same time, emerging applications require functionality that existing 
 protocols can provide only inefficiently, if at all.
 
 To begin to address this problem, the Internet Architecture Board (IAB), 
 within the scope of its IP Stack Evolution Program, is organizing a 
 workshop to discuss approaches to de-ossifying transport, especially 
 with respect to interactions with middleboxes and new methods for 
 implementing transport protocols. Recognizing that the end-to-end 
 principle has long been compromised, we start with the fundamental 
 question of matching paths through the Internet with certain 
 characteristics to application and transport requirements. Which paths 
 through the Internet are actually available to applications? Which 
 transports can be used over these paths? How can applications cooperate 
 with network elements to improve path establishment and discovery? Can 
 common transport functionality and standardization help application 
 developers to implement and deploy such approaches in today’s Internet? 
 Could cooperative approaches give us a way to rebalance the Internet 
 back toward its end-to-end roots?
 
 Topics
 
 For this workshop we would like to consider topics that speak to these 
 questions, including the following:
 
 - Development and deployment of transport-like features in application-
  layer protocols
 - Methods for discovery of path characteristics and protocol 
  availability along a path
 - Methods for middlebox detection and characterization of middlebox 
  behavior and functionality
 - Methods for NAT and middlebox traversal in the establishment of end-
  to-end paths
 - Mechanisms for cooperative path-endpoint signaling, and lessons 
  learned from existing approaches
 - Economic considerations and incentives for cooperation in middlebox 
  deployment
 
 We will explicitly focus on approaches that are incrementally deployable 
 within the present Internet.
 
 The outcome of the workshop will be architectural and engineering 
 guidance on future work in the area, published as an IAB workshop 
 report, based on discussion of proposed approaches; future work will be 
 pursued within the IAB Stack Evolution Program. We will also explore 
 possible areas for standardization, e.g. new protocols that separate 
 signaling to and from on-path devices and common transport semantics 
 from the rest of the transport protocol; and for general guidance, e.g. 
 how transports as well as middleboxes can be designed and deployed to 
 achieve these goals.
 
 Submission Instructions
 
 Attendance at the workshop is by invitation. Prospective participants 
 are invited to submit short position papers outlining their views on one 
 or more topics related to the scope of the workshop. Position papers 
 will be published on the IAB website at: 
 http://www.iab.org/activities/workshops/semi/.
 
 Submissions accepted at: 
 https://www.easychair.org/conferences/?conf=semi2015
 
 Submission Deadline: 31 October 2014
 
 Notification Deadline: 17 November 2014
 
 Workshop Dates: 26-27 January 2015
 
 Sponsored by the Internet Architecture Board, the Internet Society, and 
 ETH Zürich. Mirja Kühlewind and Brian Trammell, General Chairs.

Reappointment of Nevil Brownlee as Independent Submission Editor

[IAB Chair]

The Internet Architecture Board is pleased to announce the reappointment of
Nevil Brownlee as the Independent Submission Editor (ISE). The IAB received
a significant number of comments saying that Nevil is doing a superior job.
This appointment is for a two year term, beginning on 15 February 2015 and
ending on 14 February 2017.

On behalf of the IAB,
  Russ Housley
  IAB Chair

Re: Call for IAOC Nominations and Volunteers 2015

[IAB Chair]

Just a quick reminder: the call for volunteers is open until 5 November 2014.

Thanks for your consideration,
  Russ Housley
  IAB Chair

On Oct 8, 2014, at 10:51 AM, IAB Chair wrote:

 This is a call for nominations for the IAB appointment to the IETF 
 Administrative Oversight Committee (IAOC). The nomination period will 
 close on 5 November 2014. 
 
 IAOC membership is described in BCP 101 (RFC 4071) Section 4, with 
 selection guidelines and process documented in BCP 113 (RFC 4333).  In 
 alternate years. The IESG and the IAB each select one person for a two-
 year IAOC term.  This year, the IAB will select one person for a term 
 beginning in the Spring of 2015.  Note that NomCom is also selecting an 
 IAOC member.
 
 The incumbent is Bob Hinden.  Bob has served on the IAOC since
 March 2007, and he was IAOC Chair from 2009 to 2013.  After eight
 years on the IAOC, Bob is not seeking another term.  We thank him
 for so many years of service to the IETF community.
 
 Candidates for these IAOC positions should have knowledge of the IETF, 
 knowledge of contracts and financial procedures, and familiarity with 
 the administrative support needs of the IAB, the IESG, and the IETF 
 standards process.  Candidates are also expected to be able to 
 understand the respective roles and responsibilities of the IETF and 
 ISOC in this activity, and be able to articulate these roles within the 
 IETF community.
 
 Acceptable candidates must be prepared to exercise all the duties of an 
 IAOC member.  These responsibilities include, but are not limited to, 
 the setting (in consultation with the community and after carefully 
 considering their input) of administrative support policies, oversight 
 of the administrative operations of the IETF, and representing the 
 interests of the IETF to the IAOC.  The IAOC meets for a couple of
 hours at each IETF meeting, holds two conference calls each month,
 and meets for two days in a separate meeting, usually in May.
 Acceptable candidates must be able to undertake full participation
 in all IAOC meetings and activities.
 
 IAOC members also serve as the trustees of the IETF Trust.
 
 The IAB-selected member of the IAOC does not directly represent the IAB.  
 The IAB and IESG selected members are accountable directly to the IETF 
 community.  As such, candidates do not need to be current members of the 
 IAB or the IESG and, in fact, we prefer nominations and volunteers from 
 the rest of the community.
 
 If you are interested in one of these positions, or know of someone who 
 may be a good fit for this position, please send the name and email 
 address to iab-ch...@iab.org and ex...@iab.org.
 
 The IAB will respond with a questionnaire, asking for the candidates' 
 qualifications and willingness to serve.
 
 The names of all people who declare themselves willing to serve will be 
 made public on the ietf-announce@ietf.org list after the end of the 
 solicitation period.  The plan is to post the list of candidates by
 7 November 2014.
 
 The IAB expects to make a decision in early December 2014. 
 
 On Behalf of the IAB,
  Russ Housley
  IAB Chair
 

Call for Feedback on the current IRTF Chair

[IAB 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

Call for IAOC Nominations and Volunteers 2015

[IAB Chair]

This is a call for nominations for the IAB appointment to the IETF 
Administrative Oversight Committee (IAOC). The nomination period will 
close on 5 November 2014. 

IAOC membership is described in BCP 101 (RFC 4071) Section 4, with 
selection guidelines and process documented in BCP 113 (RFC 4333).  In 
alternate years. The IESG and the IAB each select one person for a two-
year IAOC term.  This year, the IAB will select one person for a term 
beginning in the Spring of 2015.  Note that NomCom is also selecting an 
IAOC member.

The incumbent is Bob Hinden.  Bob has served on the IAOC since
March 2007, and he was IAOC Chair from 2009 to 2013.  After eight
years on the IAOC, Bob is not seeking another term.  We thank him
for so many years of service to the IETF community.

Candidates for these IAOC positions should have knowledge of the IETF, 
knowledge of contracts and financial procedures, and familiarity with 
the administrative support needs of the IAB, the IESG, and the IETF 
standards process.  Candidates are also expected to be able to 
understand the respective roles and responsibilities of the IETF and 
ISOC in this activity, and be able to articulate these roles within the 
IETF community.

Acceptable candidates must be prepared to exercise all the duties of an 
IAOC member.  These responsibilities include, but are not limited to, 
the setting (in consultation with the community and after carefully 
considering their input) of administrative support policies, oversight 
of the administrative operations of the IETF, and representing the 
interests of the IETF to the IAOC.  The IAOC meets for a couple of
hours at each IETF meeting, holds two conference calls each month,
and meets for two days in a separate meeting, usually in May.
Acceptable candidates must be able to undertake full participation
in all IAOC meetings and activities.

IAOC members also serve as the trustees of the IETF Trust.

The IAB-selected member of the IAOC does not directly represent the IAB.  
The IAB and IESG selected members are accountable directly to the IETF 
community.  As such, candidates do not need to be current members of the 
IAB or the IESG and, in fact, we prefer nominations and volunteers from 
the rest of the community.

If you are interested in one of these positions, or know of someone who 
may be a good fit for this position, please send the name and email 
address to iab-ch...@iab.org and ex...@iab.org.

The IAB will respond with a questionnaire, asking for the candidates' 
qualifications and willingness to serve.

The names of all people who declare themselves willing to serve will be 
made public on the ietf-announce@ietf.org list after the end of the 
solicitation period.  The plan is to post the list of candidates by
7 November 2014.

The IAB expects to make a decision in early December 2014. 

On Behalf of the IAB,
  Russ Housley
  IAB Chair

No Technical Plenary Topic at IETF 91

[IAB Chair]

The IAB has decided to limit its request for plenary time to 60 minutes
for IETF 91 in Honolulu.  Reports from the IAB Chair, the IRTF Chair,
the RSE, and the RSOC Chair will take place as usual.  In addition there
will be an update on two IAB programs.  As usual, there will also be an
open mic session.  However, there will not be a technical speaker or
panel at this plenary session.  The IAB considered a number of topics,
but the plenary format did not seem to be appropriate ​for general
community discussion of them at this IETF.  One or more
workshops may instead result.  As always, suggestions for
technical plenary topics or speakers are always welcome.

On behalf of the IAB,
  Russ Housley
  IAB Chair

Call for Papers: IAB Workshop on Stack Evolution in a Middlebox Internet (SEMI)

[IAB Chair]

IAB Workshop on Stack Evolution in a Middlebox Internet (SEMI)
26-27 January 2015 – ETH Zürich, Switzerland

The Internet’s transport layer has ossified, squeezed between narrow 
interfaces (from BSD sockets to pseudo-transport over HTTPS) and 
increasing in-network modification of traffic by middleboxes that make 
assumptions about the protocols running through them. This ossification 
makes it difficult to innovate in the transport layer, through the 
deployment of new protocols or the extension of existing ones. At the 
same time, emerging applications require functionality that existing 
protocols can provide only inefficiently, if at all.

To begin to address this problem, the Internet Architecture Board (IAB), 
within the scope of its IP Stack Evolution Program, is organizing a 
workshop to discuss approaches to de-ossifying transport, especially 
with respect to interactions with middleboxes and new methods for 
implementing transport protocols. Recognizing that the end-to-end 
principle has long been compromised, we start with the fundamental 
question of matching paths through the Internet with certain 
characteristics to application and transport requirements. Which paths 
through the Internet are actually available to applications? Which 
transports can be used over these paths? How can applications cooperate 
with network elements to improve path establishment and discovery? Can 
common transport functionality and standardization help application 
developers to implement and deploy such approaches in today’s Internet? 
Could cooperative approaches give us a way to rebalance the Internet 
back toward its end-to-end roots?

Topics

For this workshop we would like to consider topics that speak to these 
questions, including the following:

- Development and deployment of transport-like features in application-
  layer protocols
- Methods for discovery of path characteristics and protocol 
  availability along a path
- Methods for middlebox detection and characterization of middlebox 
  behavior and functionality
- Methods for NAT and middlebox traversal in the establishment of end-
  to-end paths
- Mechanisms for cooperative path-endpoint signaling, and lessons 
  learned from existing approaches
- Economic considerations and incentives for cooperation in middlebox 
  deployment

We will explicitly focus on approaches that are incrementally deployable 
within the present Internet.

The outcome of the workshop will be architectural and engineering 
guidance on future work in the area, published as an IAB workshop 
report, based on discussion of proposed approaches; future work will be 
pursued within the IAB Stack Evolution Program. We will also explore 
possible areas for standardization, e.g. new protocols that separate 
signaling to and from on-path devices and common transport semantics 
from the rest of the transport protocol; and for general guidance, e.g. 
how transports as well as middleboxes can be designed and deployed to 
achieve these goals.

Submission Instructions

Attendance at the workshop is by invitation. Prospective participants 
are invited to submit short position papers outlining their views on one 
or more topics related to the scope of the workshop. Position papers 
will be published on the IAB website at: 
http://www.iab.org/activities/workshops/semi/.

Submissions accepted at: 
https://www.easychair.org/conferences/?conf=semi2015

Submission Deadline: 31 October 2014

Notification Deadline: 17 November 2014

Workshop Dates: 26-27 January 2015

Sponsored by the Internet Architecture Board, the Internet Society, and 
ETH Zürich. Mirja Kühlewind and Brian Trammell, General Chairs.

Call for Review of draft-iab-smart-object-architecture-04.txt, Architectural Considerations in Smart Object Networking

[IAB Chair]

This is a call for review of Architectural Considerations in Smart Object 
Networking prior to potential approval as an IAB stream RFC.

The document is available for inspection here: 
https://datatracker.ietf.org/doc/draft-iab-smart-object-architecture/

The Call for Review will last until 24 September 2014.  Please send comments to 
i...@iab.org.

On behalf of the IAB,
   Russ Housley
   IAB Chair

Appointment to 2015 ICANN Nominating Committee

[IAB Chair]

The IAB has selected John Levine to serve on the 2015 ICANN NOMCOM. He is 
co-author of nine RFCs, and he brings a wealth of experience in both the IETF 
and ICANN.  He is the past chair of the IRTF's AntiSpam Research Group, and he 
has more recently delved into issues relating to zone cuts.  At ICANN he is an 
active participant in the At-Large Advisory Committee (ALAC), and he has 
participated as an expert on the RSTEP committee.  The IAB wishes John every 
success in this important role, and encourages the whole community to share 
their views with John about the various ICANN leadership positions that he will 
have a part in selecting.

The IAB thanks everyone who put their name forward as a candidate for this 
position, as well as Russ Mundy for his service in this role over the last year.

On behalf of the IAB,
  Russ Housley
  IAB Chair

Re: Volunteers for the 2015 ICANN Nominating Committee

[IAB Chair]

The IAB has extended to deadline for volunteering to be a member of the 2015 
ICANN Nominating Committee (NomCom) to Friday, 25 July 2014.  If you are 
interested in serving on the ICANN NomCom, please send a short e-mail to 
iab-chair at iab.org and execd at iab.org with your motivation and information 
concerning your familiarity with the IETF and ICANN by Friday at 1320 Eastern 
(when IETF 90 ends).

Thanks,
Russ Housley
IAB Chair

On Jul 16, 2014, at 7:37 AM, IAB Chair wrote:

 I was just told that the link to the bylaws does not work.  Here is one that 
 works:
 https://www.icann.org/resources/pages/bylaws-2012-02-25-en
 
 Thanks,
 Russ Housley
 IAB Chair
 
 
 On Jul 3, 2014, at 5:04 PM, Russ Housley wrote:
 
 Dear Colleagues:
 
 The IAB (on behalf of the IETF) has been asked to supply a member to the 
 2015 ICANN Nominating Committee (NomCom) by August 2014. The IAB would 
 therefore like to ask the community for volunteers to serve on the ICANN 
 NomCom. Our current appointee, Russ Mundy is unable to serve another term.  
 The IAB thanks Russ for his service and wishes him well.
 
 If you are interested in serving on the ICANN NomCom, please send a short 
 e-mail to iab-chair at iab.org and execd at iab.org with your motivation and 
 information concerning your familiarity with the IETF and ICANN. The 
 deadline for volunteering is 19 July 2014.
 
 After asking for community input on the candidates, the IAB will select from 
 the available candidates, taking into account the familiarity with ICANN and 
 the IETF, their roles, and their processes. The selected candidate will 
 serve on the ICANN NomCom on personal title; however, we will be looking for 
 a candidate who has an understanding of the interests of the technical 
 community.
 
 The ICANN NomCom process itself is governed by the ICANN bylaws; an abstract 
 of the relevant articles can be found at http://nomcom.icann.org/bylaws.htm. 
  In addition, each NomCom determines a number of its own operational 
 procedures, including the role of the NomCom in recruiting and selecting 
 candidates for ICANN leadership positions.  Based on Russ Mundy's 
 experience, the time commitment is significant.  The selected person should 
 be prepared to participate in the recruitment of potential candidates for 
 ICANN leadership positions (a few hours per month November through April); a 
 few hours on conference calls each month (and even more near selection); ten 
 or more hours per month reviewing and assessing candidate qualifications in 
 April, May, and June; and multiple days of face-to-face meetings of the full 
 NomCom at each of the three ICANN meetings.
 
 The ICANN NomCom typically meets in person at or around three consecutive 
 ICANN meetings in various locations throughout the world, resulting next 
 summer in a final slate of candidates for the ICANN Board, the GNSO, ccNSO, 
 and ALAC.
 
 NOTE: ICANN does cover travel and hotel costs for a pre-determined number of 
 days at each of the 3 consecutive ICANN meetings.
 
 Candidates should be able to join monthly teleconferences (typically at UTC 
 14:00), with the expectation that these teleconferences will held weekly 
 during the candidate assessment process in May and June.
 
 For more information about the ICANN NomCom see: http://nomcom.icann.org/
 
 On behalf of the IAB,
 Russ Housley
 IAB Chair
 

The IAB is Seeking Feedback on the Independent Stream Editor (ISE)

[IAB Chair]

As part of its oversight responsibility for the Independent Stream, the IAB is 
solociting comments from the community on the performance of the Independent 
Stream Editor, Nevil Brownlee.  We are interested in comments on what has gone 
well or badly in the last several years of operation of the Independent Stream 
and Nevil's activities as ISE.

Please send comments to iab-chair at iab.org.  In addition, please CC 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 90 in Toronto.

Thank you,
Russ Housley
IAB Chair

Re: Volunteers for the 2015 ICANN Nominating Committee

[IAB Chair]

I was just told that the link to the bylaws does not work.  Here is one that 
works:
https://www.icann.org/resources/pages/bylaws-2012-02-25-en

Thanks,
 Russ Housley
 IAB Chair


On Jul 3, 2014, at 5:04 PM, Russ Housley wrote:

 Dear Colleagues:
 
 The IAB (on behalf of the IETF) has been asked to supply a member to the 2015 
 ICANN Nominating Committee (NomCom) by August 2014. The IAB would therefore 
 like to ask the community for volunteers to serve on the ICANN NomCom. Our 
 current appointee, Russ Mundy is unable to serve another term.  The IAB 
 thanks Russ for his service and wishes him well.
 
 If you are interested in serving on the ICANN NomCom, please send a short 
 e-mail to iab-chair at iab.org and execd at iab.org with your motivation and 
 information concerning your familiarity with the IETF and ICANN. The deadline 
 for volunteering is 19 July 2014.
 
 After asking for community input on the candidates, the IAB will select from 
 the available candidates, taking into account the familiarity with ICANN and 
 the IETF, their roles, and their processes. The selected candidate will serve 
 on the ICANN NomCom on personal title; however, we will be looking for a 
 candidate who has an understanding of the interests of the technical 
 community.
 
 The ICANN NomCom process itself is governed by the ICANN bylaws; an abstract 
 of the relevant articles can be found at http://nomcom.icann.org/bylaws.htm.  
 In addition, each NomCom determines a number of its own operational 
 procedures, including the role of the NomCom in recruiting and selecting 
 candidates for ICANN leadership positions.  Based on Russ Mundy's experience, 
 the time commitment is significant.  The selected person should be prepared 
 to participate in the recruitment of potential candidates for ICANN 
 leadership positions (a few hours per month November through April); a few 
 hours on conference calls each month (and even more near selection); ten or 
 more hours per month reviewing and assessing candidate qualifications in 
 April, May, and June; and multiple days of face-to-face meetings of the full 
 NomCom at each of the three ICANN meetings.
 
 The ICANN NomCom typically meets in person at or around three consecutive 
 ICANN meetings in various locations throughout the world, resulting next 
 summer in a final slate of candidates for the ICANN Board, the GNSO, ccNSO, 
 and ALAC.
 
 NOTE: ICANN does cover travel and hotel costs for a pre-determined number of 
 days at each of the 3 consecutive ICANN meetings.
 
 Candidates should be able to join monthly teleconferences (typically at UTC 
 14:00), with the expectation that these teleconferences will held weekly 
 during the candidate assessment process in May and June.
 
 For more information about the ICANN NomCom see: http://nomcom.icann.org/
 
 On behalf of the IAB,
  Russ Housley
  IAB Chair

Appointment of Matt Miller as IETF Liaison Manager to ECMA TC39

[IAB Chair]

ECMA:

The IAB has appointed Matt Miller to serve as IETF liaison manager to ECMA 
TC39.  Matt works at Cisco Systems and is also currently the chair of the JSON 
working group.

The IAB thanks Matt for putting his name forward, and wishes him success in 
this new role.

On behalf of the IAB,
  Russ Housley
  IAB Chair

Call for Nominations: 2015 Applied Networking Research Prize (ANRP)

[IAB Chair]

CALL FOR NOMINATIONS:
 APPLIED NETWORKING RESEARCH PRIZE (ANRP) 2015

http://irtf.org/anrp


*** Submit nominations for the 2015 award period of the  ***
***  Applied Networking Research Prize until October 31, 2014!   ***


The Applied Networking Research Prize (ANRP) is awarded for recent
results in applied networking research that are relevant for
transitioning into shipping Internet products and related
standardization efforts. Researchers with relevant, recent results
are encouraged to apply for this prize, which will offer them the
opportunity to present and discuss their work with the engineers,
network operators, policy makers and scientists that participate in
the Internet Engineering Task Force (IETF) and its research arm, the
Internet Research Task Force (IRTF). Third-party nominations for this
prize are also encouraged. The goal of the Applied Networking
Research Prize is to recognize the best new ideas in networking, and
bring them to the IETF and IRTF especially in cases where they would
not otherwise see much exposure or discussion.

The Applied Networking Research Prize (ANRP) consists of:

• cash prize of $500 (USD)
• invited talk at the IRTF Open Meeting
• travel grant to attend a week-long IETF meeting (airfare, hotel,
 registration, stipend)
• recognition at the IETF plenary
• invitation to related social activities
• potential for additional travel grants to future IETF meetings,
 based on community feedback

The Applied Networking Research Prize will be awarded once per
calendar year. Each year, several winners will be chosen and invited
to present their work at one of the three IETF meetings during the
year.


HOW TO NOMINATE

Only a single person can be nominated for the award. The basis of the
nomination is a peer-reviewed, original journal, conference or
workshop paper they authored, which was recently published or
accepted for publication. The nominee must be one of the main authors
of the nominated paper. Both self nominations (nominating one’s own
paper) and third-party nominations (nominating someone else’s paper)
are encouraged.

The nominated paper should provide a scientific foundation for
possible future IETF engineering work or IRTF research and
experimentation, analyze the behavior of Internet protocols in
operational deployments or realistic testbeds, make an important
contribution to the understanding of Internet scalability,
performance, reliability, security or capability, or otherwise be of
relevance to ongoing or future IETF or IRTF activities.

Applicants must briefly describe how the nominated paper relates to
these goals, and are encouraged to describe how a presentation of
these research results would foster their transition into new IETF
engineering or IRTF experimentation, or otherwise seed new activities
that will have an impact on the real-world Internet.

The goal of the Applied Networking Research Prize (ANRP) is to foster
the transitioning of research results into real-world benefits for
the Internet. Therefore, applicants must indicate that they (or the
nominee, in case of third-party nominations) are available to attend
at least one of the year’s IETF meetings in person and in its
entirety.

Nominations must include:

• the name and email address of the nominee
• a bibliographic reference to the published (or accepted)
 nominated paper
• a PDF copy of the nominated paper
• a statement that describes how the nominated paper fulfills the
 goals of the award
• a statement about which of the year’s IETF meetings the nominee
 would be available to attend in person and in its entirety
• a brief biography or CV of the nominee
• optionally, any other supporting information (link to nominee’s
 web site, etc.)

Nominations are submitted via the submission site at
http://irtf.org/anrp/2015/. In exceptional cases, nominations may
also be submitted by email to a...@irtf.org.


IMPORTANT DATES

Applications close: October 31, 2014 (hard)
Notifications:  December 1, 2014


SPONSORS

The Applied Networking Research Prize (ANRP) is supported by the
Internet Society (ISOC), as part of its Internet Research Award
Programme, in coordination with the Internet Research Task Force
(IRTF).


HELP PUBLICIZE THE ANRP

If you would like to help publicize the ANRP within your
organization, you are welcome to print and use the flyer at
http://irtf.org/anrp-2015-flyer.pdf

I* Post-NETmundial Meeting Statement

[IAB Chair]

I* Post-NETmundial Meeting Statement -- 13 May 2014

Leaders of the organizations responsible for coordination of the Internet 
technical infrastructure (loosely referred to as I* leaders) met on 25 April 
in São Paulo, Brazil following the NETmundial meeting. During the 1-day I* 
leaders meeting, the group considered a range of issues where dialogue among 
Internet technical organizations is useful.

In particular, the group highlighted that the NETmundial meeting has energized 
the multistakeholder discussions and model in a positive fashion. The leaders 
highlighted the importance of open, collaborative, bottom-up processes across 
meetings and organisations dealing with the Internet.

During the meeting, the group reflected on a number of other topics as well:

I. Transition of NTIA's Stewardship of the IANA Functions 
(http://www.icann.org/en/about/agreements/iana/transition) and review of ICANN 
accountability processes;

II. The announcement made by ICANN CEO of the launch of a process to review and 
improve ICANN's own oversight/accountability mechanism and how it is 
complementary to the IANA function’s stewardship evolution process.

III. Upcoming Internet Governance meetings including the Internet Governance 
Forum (http://www.intgovforum.org) and the ITU Plenipotentiary Conference 
(http://www.internetsociety.org/plenipotbackground)

IV. Coordination of experiences, plans and resources to further deploy DNSSEC 
via the ccTLD community

V. Identification of issues and players to further enable adoption of 
Internationalised Domain Names (IDNs) toward accelerating their adoption in 
communities that don’t use the Latin Character sets.

The group bade farewell to Raúl Echeberría, CEO of LACNIC and Leslie Daigle, 
Chief Internet Technology Officer of the Internet Society.

 
Participating Leaders:
Adiel A. Akplogan, CEO African Network Information Center (AFRINIC)
Barrack Otieno, Manager, The African Top Level Domains 
Organization(AFTLD)
Paul Wilson, Director General Asia-Pacific Network Information 
Centre(APNIC)
Don Hollander, General Manager Asia Pacific Top Level Domain 
Association (APTLD)
John Curran, CEO American Registry for Internet Numbers (ARIN)
Peter Van Roste, General Manager, Council for European National Top 
Level Domain Registries (CENTR)
Russ Housley, Chair Internet Architecture Board (IAB)
Fadi Chehadé, President and CEO Internet Corporation for Assigned Names 
and Numbers (ICANN)
Jari Arkko, Chair Internet Engineering Task Force (IETF)
Kathy Brown, President and CEO Internet Society (ISOC)
Raúl Echeberría, CEO Latin America and Caribbean Internet Addresses 
Registry (LACNIC)
Carolina Aguerre, General Manager, Latin American and Caribbean TLD 
Association (LACTLD)
Axel Pawlik, Managing Director Réseaux IP Européens Network 
Coordination Centre (RIPE NCC)
Tim Berners-Lee, Director, World Wide Web Consortium (W3C)

Appointment of Sean Turner to the ISOC Board of Trustees

[IAB Chair]

The Internet Society (ISOC) provides organizational and financial support for 
the IETF.  As part of the arrangements between ISOC and the IETF, the IETF is 
called upon to name three Trustees to its Board, with staggered 3 year terms. 
This requires that the IETF select one Trustee each year.  The IAB does this 
selection following the process in RFC 3677.
 
I am pleased to announce that the IAB has selected Sean Turner for a term on 
the ISOC BoT.  His term will start in mid-2014 and end in mid-2017.

On behalf of the IAB,
Russ Housley
IAB Chair

RFC Series Oversight Committee (RSOC) Appointments

[IAB Chair]

The IAB extends many thanks to the community members that were willing to serve 
on the RSOC for their ongoing support of the RFC Series and the RFC Series 
Editor.

After reviewing the strong list of individuals who offered to serve on the 
RSOC, the IAB is appointing two people to the RSOC:
Sarah Banks
Robert Sparks

The IAB sincerely thanks all of the people that offered to serve on the RSOC.

On behalf of the IAB,
   Russ Housley
   IAB Chair


On Mar 26, 2014, at 11:29 AM, IAB Chair wrote:

 As specified in RFC Editor Model (Version 2) (RFC 6635), the IAB is 
 responsible for appointing the members of the RFC Series Oversight Committee 
 (RSOC).  Bernard Aboba has stepped down from his role on the RSOC.  The IAB 
 thanks him for his service.
 
 The IAB is now looking for a community member to appoint to the RSOC. This 
 message is a call for nominations for that position.  If you are interested, 
 or there is someone you know of who would make a good member, please nominate 
 yourself or that person.
 
 As noted in RFC 6635, the RSOC, which currently includes two IAB members, 
 acts with authority delegated from the IAB, and the RSOC is responsible for 
 approving consensus policy and vision documents developed by the RFC Series 
 Editor (RSE) in collaboration with the community.  The RSOC is also 
 responsible for ensuring that the RFC Series is run in a transparent and 
 accountable manner.  For decisions that affect the RFC Series Editor 
 individually, the RSOC prepares recommendations for the IAB, such as 
 preparing the performance reviews of the RSE.  RSOC members are expected to 
 recognize potential conflicts of interest and behave accordingly.
 
 If you would like to nominate a candidate for membership in the RSOC, please 
 send information on the candidate, including their email address, to 
 iab-chair at iab.org and execd at iab.org.  Self-nominations are acceptable.
 
 The current membership of the RSOC can be seen at 
 http://www.iab.org/activities/programs/rfc-editor-program/.
 
 Nominations should be received by 8 April 2014.
 
 The IAB will confirm individuals willingness to be considered, and publish 
 the resulting list so that the community can provide comments before the IAB 
 makes any decisions on RSOC membership.
 
 The new member will begin serving on the RSOC as soon as the IAB completes 
 the selection process.
 
 For the information of potential nominees, the RSOC will be having a half-day 
 face-to-face meeting in Toronto on 19 July 2014, the Saturday before IETF 90.
 
 The current focus of the RSOC is on:
 
 1) Overseeing and assisting the RSE in the process of evoling the RFC format 
 and style.
 
 2) Periodic reviews of the RFSE performance.
 
 3) Working with the RSE and the IETF Administrative Oversight Committee 
 (IAOC) on the statements of work for contracts related to the RFC Production 
 Center and RFC Publisher.
 
 The RSOC usually meets virtually once a month for an hour, a lunch at every 
 IETF meeting, and a half day in-person meeting once a year (usually scheduled 
 the weekend before an IETF meeting at the same venue (as noted above the next 
 one will be in Toronto).  More time may be required if the applicant 
 participates in leadership of the committee, design teams, or other related 
 activities. RSOC members are expected to follow the rfc-interest mailing 
 list, a usually low-volume list for internal communication, and to be 
 familiar with discussion topics related to the RFC series on the 
 i...@ietf.org list.
 
 Thank you,
 Russ Housley
 IAB Chair
 

Call for volunteers for C/C++ API liaison manager

[IAB Chair]

We often see proposals for APIs (most commonly C APIs) discussed in the IETF.  
ISO/IEC JTC1/SC22 is the standards body for various programming languages, 
notably including C (WG14) and C++ (WG21), and those groups have been working 
on APIs for various IETF technologies, including URIs, sockets, IP addresses, 
etc.  The IAB is considering whether to request a liaison relationship with 
ISO/IEC JTC1/SC22 and is seeking to determine if there are candidates willing 
to serve as a liaison manager before determining whether to request the 
relationship.  For details on what a liaison manager position entails, see RFC 
4052, RFC 4053, and RFC 4691.
 
Volunteers are requested to send email to i...@iab.org by May 28, 2014.

On behalf of the IAB,
Russ Housley
IAB Chair

IAB Sends Comments to ICANN on the Transition NTIA’s Stewardship of the IANA Functions

[IAB Chair]

Today, the IAB sent comments regarding the “Draft Proposal, Based on Initial 
Community Feedback, of the Principles and Mechanisms and the Process to Develop 
a Proposal to Transition NTIA’s Stewardship of the IANA Functions”.  The 
comments are on the IAB web site:
http://www.iab.org/wp-content/IAB-uploads/2014/04/iab-response-to-20140408-20140428a.pdf

Thanks for your consideration,
  Russ Housley
  IAB Chair

Call for Review of draft-iab-itat-report, Report from the IAB workshop on Internet Technology Adoption and Transition (ITAT)

[IAB Chair]

This is a call for review of Report from the IAB workshop on Internet 
Technology Adoption and Transition (ITAT) prior to potential approval as an 
IAB stream RFC.

The document is available for inspection here:
https://datatracker.ietf.org/doc/draft-iab-itat-report-/

The Call for Review will last until 16 May 2014.  Please send comments to 
i...@iab.org. 

On behalf of the IAB,
Russ Housley
IAB Chair

Call for Review of draft-iab-cc-workshop-report-01, Report from the IAB/IRTF Workshop on Congestion Control for Interactive Real-Time Communication

[IAB Chair]

This is a call for review of Report from the IAB/IRTF Workshop on Congestion 
Control for Interactive Real-Time Communication prior to potential approval as 
an IAB stream RFC.

The document is available for inspection here:
https://datatracker.ietf.org/doc/draft-iab-cc-workshop-report/

The Call for Review will last until 14 May 2014.  Please send comments to 
i...@iab.org. 

On behalf of the IAB,
 Russ Housley
 IAB Chair

Request for Feedback on RFC Series Oversight Committee (RSOC) Nominations

[IAB Chair]

The IAB announced a call for nominations and volunteers for serving on
the RSOC on 26 March 2014.  For details on the position and further
links, please see the previous message here:
https://mailarchive.ietf.org/arch/msg/ietf-announce/nAOM54TxJOtg_wFfmnKXoSSf594

The call completed, and xx people accepted nominations.  As specified in
the announcement, the IAB is now providing that list to the community.
If you have opinions, information, or perspectives on the individuals for
the RSOC which you believe would help the IAB select the RSOC membership,
please provide comments to iab-chair at iab.org and execd at iab.org.
Please provide feedback before 23 April 2014.

With thanks for their willingness to serve, the list of willing nominees:

- Sara Banks
- Donald Eastlake
- Paul Hoffman
- Robert Sparks

Thank you,
  Russ Housley
  IAB Chair 

Comments from the IAB on NISTIR 7977

[IAB Chair]

Today, the IAB sent comments to the US National Institute for Standards and 
Technology (NIST) in the matter of the draft NISTIR 7977 (NIST Cryptographic 
Standards and Guidelines Development Process).  In the statement, the IAB 
supports transparency and openness, encouraging NIST to make improvements for 
not only Federal Information Processing Standards, but also Recommendations and 
Special Publications.

The Draft NISTIR 7977 is available from the NIST website: 
http://csrc.nist.gov/publications/drafts/nistir-7977/nistir_7977_draft.pdf

The IAB statement is available from the IAB website: 
http://www.iab.org/wp-content/IAB-uploads/2014/04/IAB-NIST7977-20140407.pdf

On behalf of the IAB,
Russ Housley
IAB Chair

Reminder: Call for RFC Series Oversight Committee (RSOC) Nominations

[IAB Chair]

Please submit nominations by 8 April 2014.

Thanks,
  Russ


Begin forwarded message:

 From: IAB Chair iab-ch...@iab.org
 Date: March 26, 2014 11:29:38 AM EDT
 To: IETF Announce ietf-announce@ietf.org
 Cc: IAB i...@iab.org, IETF i...@ietf.org
 Subject: Call for RFC Series Oversight Committee (RSOC) Nominations
 
 As specified in RFC Editor Model (Version 2) (RFC 6635), the IAB is 
 responsible for appointing the members of the RFC Series Oversight Committee 
 (RSOC).  Bernard Aboba has stepped down from his role on the RSOC.  The IAB 
 thanks him for his service.
 
 The IAB is now looking for a community member to appoint to the RSOC. This 
 message is a call for nominations for that position.  If you are interested, 
 or there is someone you know of who would make a good member, please nominate 
 yourself or that person.
 
 As noted in RFC 6635, the RSOC, which currently includes two IAB members, 
 acts with authority delegated from the IAB, and the RSOC is responsible for 
 approving consensus policy and vision documents developed by the RFC Series 
 Editor (RSE) in collaboration with the community.  The RSOC is also 
 responsible for ensuring that the RFC Series is run in a transparent and 
 accountable manner.  For decisions that affect the RFC Series Editor 
 individually, the RSOC prepares recommendations for the IAB, such as 
 preparing the performance reviews of the RSE.  RSOC members are expected to 
 recognize potential conflicts of interest and behave accordingly.
 
 If you would like to nominate a candidate for membership in the RSOC, please 
 send information on the candidate, including their email address, to 
 iab-chair at iab.org and execd at iab.org.  Self-nominations are acceptable.
 
 The current membership of the RSOC can be seen at 
 http://www.iab.org/activities/programs/rfc-editor-program/.
 
 Nominations should be received by 8 April 2014.
 
 The IAB will confirm individuals willingness to be considered, and publish 
 the resulting list so that the community can provide comments before the IAB 
 makes any decisions on RSOC membership.
 
 The new member will begin serving on the RSOC as soon as the IAB completes 
 the selection process.
 
 For the information of potential nominees, the RSOC will be having a half-day 
 face-to-face meeting in Toronto on 19 July 2014, the Saturday before IETF 90.
 
 The current focus of the RSOC is on:
 
 1) Overseeing and assisting the RSE in the process of evoling the RFC format 
 and style.
 
 2) Periodic reviews of the RFSE performance.
 
 3) Working with the RSE and the IETF Administrative Oversight Committee 
 (IAOC) on the statements of work for contracts related to the RFC Production 
 Center and RFC Publisher.
 
 The RSOC usually meets virtually once a month for an hour, a lunch at every 
 IETF meeting, and a half day in-person meeting once a year (usually scheduled 
 the weekend before an IETF meeting at the same venue (as noted above the next 
 one will be in Toronto).  More time may be required if the applicant 
 participates in leadership of the committee, design teams, or other related 
 activities. RSOC members are expected to follow the rfc-interest mailing 
 list, a usually low-volume list for internal communication, and to be 
 familiar with discussion topics related to the RFC series on the 
 i...@ietf.org list.
 
 Thank you,
 Russ Housley
 IAB Chair
 

IAB Executive Administrative Manager

[IAB Chair]

With Mary Barnes transitioning into a voting seat on the IAB from her role as 
the IAB Executive Director, the IAB has taken the opportunity to review the job 
responsibilities associated with the IAB Executive Director and IAB Executive 
Assistant roles.  

Cindy Morgan has served as the IAB Executive Assistant since March 2011.  Based 
on the revised list of job responsibilities, the IAB has changed Cindy Morgan's 
title to IAB Executive Administrative Manager.

Based on the IAB's recommendation, the IAB Chair decided to leave the IAB 
Executive Director position vacant.

On behalf of the IAB,
  Russ Housley
  IAB Chair

Call for RFC Series Oversight Committee (RSOC) Nominations

[IAB Chair]

As specified in RFC Editor Model (Version 2) (RFC 6635), the IAB is 
responsible for appointing the members of the RFC Series Oversight Committee 
(RSOC).  Bernard Aboba has stepped down from his role on the RSOC.  The IAB 
thanks him for his service.

The IAB is now looking for a community member to appoint to the RSOC. This 
message is a call for nominations for that position.  If you are interested, or 
there is someone you know of who would make a good member, please nominate 
yourself or that person.

As noted in RFC 6635, the RSOC, which currently includes two IAB members, acts 
with authority delegated from the IAB, and the RSOC is responsible for 
approving consensus policy and vision documents developed by the RFC Series 
Editor (RSE) in collaboration with the community.  The RSOC is also responsible 
for ensuring that the RFC Series is run in a transparent and accountable 
manner.  For decisions that affect the RFC Series Editor individually, the RSOC 
prepares recommendations for the IAB, such as preparing the performance reviews 
of the RSE.  RSOC members are expected to recognize potential conflicts of 
interest and behave accordingly.

If you would like to nominate a candidate for membership in the RSOC, please 
send information on the candidate, including their email address, to iab-chair 
at iab.org and execd at iab.org.  Self-nominations are acceptable.

The current membership of the RSOC can be seen at 
http://www.iab.org/activities/programs/rfc-editor-program/.

Nominations should be received by 8 April 2014.

The IAB will confirm individuals willingness to be considered, and publish the 
resulting list so that the community can provide comments before the IAB makes 
any decisions on RSOC membership.

The new member will begin serving on the RSOC as soon as the IAB completes the 
selection process.

For the information of potential nominees, the RSOC will be having a half-day 
face-to-face meeting in Toronto on 19 July 2014, the Saturday before IETF 90.

The current focus of the RSOC is on:

1) Overseeing and assisting the RSE in the process of evoling the RFC format 
and style.

2) Periodic reviews of the RFSE performance.

3) Working with the RSE and the IETF Administrative Oversight Committee (IAOC) 
on the statements of work for contracts related to the RFC Production Center 
and RFC Publisher.

The RSOC usually meets virtually once a month for an hour, a lunch at every 
IETF meeting, and a half day in-person meeting once a year (usually scheduled 
the weekend before an IETF meeting at the same venue (as noted above the next 
one will be in Toronto).  More time may be required if the applicant 
participates in leadership of the committee, design teams, or other related 
activities. RSOC members are expected to follow the rfc-interest mailing list, 
a usually low-volume list for internal communication, and to be familiar with 
discussion topics related to the RFC series on the i...@ietf.org list.

Thank you,
 Russ Housley
 IAB Chair

Re: Guiding the Evolution of the IANA Protocol Parameter Registries

[IAB Chair]

Existing IETF and IAB consensus concerning protocol parameter registry
functions and IANA are documented in a variety of RFCs and IAB
communications [RFC2860,RFC6220,IAB1,IAB2].  Since these functions and
IANA are likely to be the subject of discussion in a number of venues
outside the IETF over the coming months and years, the IAB sought
community feedback about operating principles to use in these
discussions.  This note incorporates the comments from the mail list
discussion and the IGOVUPDATE session at IETF 89.

The IAB recognizes significant community support for these principles.

Some of these principles might seem a bit generic, but it is difficult to
predict the nature of future discussions in which IETF and IAB leaders
might find themselves, so generality helps in that regard.

On behalf of the IAB,
  Russ Housley
  IAB Chair

= = = = = = = =

Principles Guiding the Evolution of the IANA Protocol Parameter Registries

These principles must be taken together.  Ordering is not significant.

1.  The IETF protocol parameter registry function has been and continues
to be capably provided by the Internet technical community.

The strength and stability of the function and its foundation within the
Internet technical community are both important given how critical
protocol parameters are to the proper functioning of IETF protocols.

We think the structures that sustain the protocol parameter registry
function needs be strong enough that they can be offered independently by
the Internet technical community, without the need for backing from
external parties.  And we believe we largely are there already, although
the system can be strengthened further, and continuous improvements are
being made.

2. The protocol parameter registry function requires openness,
transparency, and accountability.

Existing documentation of how the function is administered and overseen
is good [RFC2860,RFC6220].  Further articulation and clarity may be
beneficial.  It is important that the whole Internet community can
understand how the function works, and that the processes for registering
parameters and holding those who oversee the protocol parameter function
accountable for following those processes are understood by all
interested parties.  We are committed to making improvements here if
necessary.

3. Any contemplated changes to the protocol parameter registry function
should respect existing Internet community agreements.

The protocol parameter registry is working well.  The existing Memorandum
of Understanding [RFC2860] defines the technical work to be carried out
by the Internet Assigned Numbers Authority on behalf of the Internet
Engineering Task Force and the Internet Research Task Force.  Any
modifications to the protocol parameter registry function should be made
using the IETF process to update RFC 6220 and other relevant RFCs.  Put
quite simply: evolution, not revolution.

4. The Internet architecture requires and receives capable service by 
Internet registries.

The stability of the Internet depends on capable provision of not just
IETF protocol parameters, but IP numbers, domain names, and other
registries.  Furthermore, DNS and IPv4/IPv6 are IETF-defined protocols.
Thus we expect the role of the IETF in standards development, architectural
guidance, and allocation of certain name/number parameters to continue.
IP multicast addresses and special-use DNS names are two examples where
close coordination is needed.  The IETF will continue to coordinate with
ICANN, the RIRs, and other parties that are mutually invested in the
continued smooth operation of the Internet registries. We fully
understand the need to work together.

5. The IETF will continue management of the protocol parameter registry
function as an integral component of the IETF standards process and the
use of resulting protocols.

RFC 6220 specifies the role and function of the protocol parameters
registry, which is critical to IETF standards processes and IETF
protocols.  The IAB, on behalf of the IETF, has the responsibility to
define and manage the relationship with the protocol registry operator
role.  This responsibility includes the selection and management of the
protocol parameter registry operator, as well as management of the
parameter registration process and the guidelines for parameter
allocation.

6. The protocol parameters registries are provided as a public service.

Directions for the creation of protocol parameter registries and the
policies for subsequent additions and updates are specified in RFCs.
The protocol parameters registries are available to everyone, and they
are published in a form that allows their contents to be included in
other works without further permission.  These works include, but are
not limited to, implementations of Internet protocols and their
associated documentation.

An important observation: The administration of the protocol parameter
registry functions by ICANN is working well for the Internet

List of Accepted Nominations for the IETF appointment to the ISOC BoT

[IAB Chair]

Dear Colleagues,

The IAB is responsible for selecting an individual to serve a 3 year 
term on the ISOC Board of Trustees.  The procedure is described in 
RFC3677. The candidates who accepted their nominations are:

- Bernard Aboba 
- Hago Dafalla 
- John Levine
- Jordi Palet Martinez 
- Kaveh Ranjbar 
- Sean Turner 
- Stephen Kent 
- Sue Hares 

We solicit feedback on these candidates by March 31, 2014.  Please send 
your response to iab-ch...@iab.org or ex...@iab.org.  If  you would like 
your feedback to be anonymized, please indicate such in your response.
The IAB expects to finalize its selection on or before April 10, 2014.

The IESG will confirm the candidate by May 25, 2014 and the appointee 
will begin serving as the new board of trustee member in June.

Kind regards,

--Russ Housley
 IAB-Chair

Call for Review of draft-iab-host-firewalls-02.txt, Reflections On Host Firewalls

[IAB Chair]

This is a call for review of Reflections On Host Firewalls
prior to potential approval as an IAB stream RFC.

The document is available for inspection here:
https://datatracker.ietf.org/doc/draft-iab-host-firewalls/

The Call for Review will last until 2 April 2014.
Please send comments to i...@iab.org. 

On behalf of the IAB,
 Russ Housley
 IAB Chair

Call for Review of draft-iab-doi-01.txt, Assigning Digital Object Identifiers to RFCs

[IAB Chair]

This is a call for review of Assigning Digital Object Identifiers
to RFCs prior to potential approval as an IAB stream RFC.

The document is available for inspection here:
https://datatracker.ietf.org/doc/draft-iab-doi/

The Call for Review will last until 2 April 2014.
Normally, we ask for comments to go to the IAB mail list, but for
this document, it is more appropriate to use the RFC Interest list.
Please send comments to rfc-inter...@rfc-editor.org. 

On behalf of the IAB,
Russ Housley
IAB Chair

Guiding the Evolution of the IANA Protocol Parameter Registries

[IAB Chair]

Existing IETF and IAB consensus concerning Internet registry functions
and IANA are documented in a variety of RFCs and IAB communications
[RFC2860,RFC6220,IAB1,IAB2].  Since registry functions and IANA are
likely to be the subject of discussion in a number of venues outside the
IETF over the coming months and years, the IAB is seeking community
feedback about operating principles to use when they find themselves
involved in those discussions.

While dealing with these issues the IAB has consistently approached the
issues from a set of (implicit) principles.  Since the registry functions
are subject of discussion in various fora, the IAB has tried to make
these operating principles explicit and seeks to confirm these with the
community.

The IAB are planning to use part of the time in the IGOVUPDATE session at
IETF 89 (6 March 2014, 17:00-18:30 GMT) for a discussion of such operating
principles.  But we wanted to kick-start that discussion with a few
thoughts about principles that the IAB and IETF have articulated in
various documents already and some that have emerged over time but may
not have been written down.  What we are interested in is an articulation
of what the IETF community values.  What other parties (ICANN, RIRs,
governments, etc.) value when they think about registry functions is
interesting, but we want to focus this discussion on the IETF and not
those other parties.

This is a first cut of making the principles more explicit for which we
seek your views.

Some of these might seem a bit generic, but it is difficult to predict
the nature of future discussions in which IETF and IAB leaders might find
themselves, so generality helps in that regard.

On behalf of the IAB,
  Russ Housley
  IAB Chair

= = = = = = = =

Principles Guiding the Evolution of the IANA Protocol Parameter Registries

1. The IETF protocol parameters function has been and continues to be
capably provided by the Internet community.

The strength and stability of the function and its foundation within the
Internet community are both important given how critical protocol
parameters are to the proper functioning of IETF protocols.

We think the structures that sustain the protocol parameters function
needs be strong enough that they can be offered independently by the
Internet community, without the need for backing from external parties.
And we believe we largely are there already, although the system can be
strengthened further, and continuous improvements are being made.

2. The administration of the protocol parameters function by ICANN is
working well for the Internet and the IETF.

We are pleased with the publication and maintenance of the protocol
parameter function and the coordination of the evaluation of
registration requests through the IANA function provided by ICANN.

3. The IETF protocol parameters function requires openness,
transparency, and accountability.

Existing documentation of how the function is administered and overseen
is good [RFC2860,RFC6220], but further articulation and clarity may be
beneficial. It is important that the whole Internet community can
understand how the function works, and that the processes for
registering parameters and holding those who oversee the protocol
parameter function accountable for following those processes are
understood by all interested parties. We are committed to making
improvements here if necessary.

4. Any contemplated changes to the protocol parameters function should
use the current RFCs and model as the starting point.

The protocol parameters function is working well, and as a result
wholesale changes to the role of the IETF vis a vis the function are not
warranted. The IETF/IANA Memorandum of Understanding [RFC2860] is a good
model to work from in the event that other parties do want to contemplate
changes. Put quite simply: evolution, not revolution.

5. The Internet architecture requires and receives capable service by 
Internet registries.

The stability of the Internet depends on capable provision of not just
IETF protocol parameters, but IP numbers, domain names, and other
registries. Furthermore, DNS and IPv4/IPv6 are IETF-defined protocols.
Thus we expect the role of the IETF in standards development, architectural
guidance, and allocation of certain name/number parameters to continue.
IP multicast addresses and special-use DNS names are two examples where
close coordination is needed.  The IETF will continue to coordinate with
ICANN, the RIRs, and other parties that are mutually invested in the
continued smooth operation of the Internet registries. We fully
understand the need to work together.

6.  The IETF will continue its direction and stewardship of the protocol
parameters function as an integral component of the IETF standards
process and the use of resulting protocols.

RFC 6220 specifies the role and function of the protocol parameters
registry, which is critical to IETF standards processes and IETF
protocols.  We see no need to revisit

Call for nominations: IETF appointment to the ISOC Board of Trustees

[IAB Chair]

The Internet Society (ISOC) provides organizational and financial support for 
the IETF. As part of the arrangements between ISOC and the IETF, the IETF is 
called upon to name 3 Trustees to its Board (BoT), with staggered 3 year terms. 
This requires that the IETF select one Trustee each year. 
 
This year, the IAB will select one person for a term ending in mid-2017. 
 
A description of the IAB's process for selecting the Trustee each year can be 
found in RFC 3677, with this year's timeline as follows: 
 
* January 30, 2014 : Open nomination period

* February 27, 2014 : Close of the nomination period 

* No later than April 10, 2014 : IAB selection delivered to IESG for 
confirmation

* No later than May 23, 2014 : Delivery of final confirmed selection to the 
ISOC Elections Committee for announcement with the rest of the new ISOC BoT 
slate. 
 
 
Nominations 
--- 
 
Nominations (including self-nominations) should be sent to the IAB -- 
i...@iab.org.  Please include e-mail contact details with the nomination. 
  
Nomination Details 
- 
 
Nominees should be aware that ISOC Trustees are elected to three year terms 
with approximately one third of the Board of Trustees elected each year. The 
responsibilities of a Trustee include fiscal management of the Internet 
Society, fundraising, and participation in Board meetings plus conference-call 
meetings, as detailed by the ISOC Bylaws:
http://www.internetsociety.org/who-we-are/governance-and-policies/amended-and-restated-laws-internet-society

The desirable characteristics of a candidate that are specific to the 
IETF-selected ISOC BoT member are outlined in section 2 of RFC 3677. 
 
Nominees are asked to provide to the IAB: 
 
1. Confirmation of their willingness to be considered within this process. 
 
2. Full name and contact information. 
 
3. A statement confirming willingness and ability to devote an appropriate 
level of time to activities associated with the position of Trustee. 
 
4. A brief biography outlining experience and background. 
 
5. A statement of interests, concerns about the Internet Society, goals as a 
Trustee, and motivation to serve as a Trustee. 
 
6. Any further information that is relevant to the work of the IAB in 
considering your nomination. 
 
Time Commitment 
--- 
 
Trustees are expected to commit the time necessary to perform regular board and 
committee business. Trustees are also expected to allocate some time to attend 
and prepare for meetings. 

 
Care of Personal Information 
 
 
The following procedures will be used by the IAB in managing this process: 
 
- The candidate's name will be published, with all other candidate names, at 
the close of the nominations period.
 
- Excerpts of the information provided to the IAB by the nominated candidate 
will be passed to the IESG as part of the confirmation process. The IESG will 
be requested to maintain confidentiality of the candidate's information.
 
- Except as noted above, all information provided to the IAB during this 
process will be kept confidential to the IAB. 

 
Current IETF-Selected Trustees 
--

The current IETF-Selected ISOC Trustees and their term of appointment are: 
 
- Bert Wijnen 2011 - 2014
- Eric Burger 2012 - 2015
- Bob Hinden 2013 - 2016 


On behalf of the IAB,
Russ Housley
IAB Chair

Call for Review of draft-iab-filtering-considerations-06.txt, Technical Considerations for Internet Service Blocking and Filtering

[IAB Chair]

This is a call for review of Technical Considerations for Internet
Service Blocking and Filtering prior to potential approval as an
IAB stream RFC.

The document is available for inspection here:
https://datatracker.ietf.org/doc/draft-iab-filtering-considerations/

The Call for Review will last until 26 February 2014.
Please send comments to i...@iab.org. 

On behalf of the IAB,
  Russ Housley
  IAB Chair

W3C/IAB workshop on Strengthening the Internet Against Pervasive Monitoring (STRINT)

[IAB Chair]

W3C/IAB workshop on Strengthening the Internet 
Against Pervasive Monitoring (STRINT)
==

Logistics/Dates:

Submissions due: Jan 15 2014
Invitations issued: Jan 31 2014
Workshop Date: Feb 28 (pm)  Mar 1 (am) 2014 
To be Confirmed - could be all day Mar 1
Location: Central London, UK. IETF Hotel or nearby (TBC)
For queries, contact: stephen.farr...@cs.tcd.ie, t...@strews.eu
Send submissions to: group-strint-submiss...@w3.org
Workshop web site: http://www.w3.org/2014/strint/

The Vancouver IETF plenary concluded that pervasive monitoring
represents an attack on the Internet, and the IETF has begun to
carry out various of the more obvious actions [1] required to
try to handle this attack. However, there are additional much
more complex questions arising that need further consideration
before any additional concrete plans can be made.

The W3C and IAB will therefore host a one-day workshop on the
topic of Strengthening the Internet Against Pervasive
Monitoring before IETF-89 in London in March 2014, with support
from the EU FP7 STREWS [2] project.  

Pervasive monitoring targets protocol data that we also need for
network manageability and security. This data is captured and
correlated with other data. There is an open problem as to how
to enhance protocols so as to maintain network manageability and
security but still limit data capture and correlation. 

The overall goal of the workshop is to steer IETF and W3C work
so as to be able to improve or strengthen the Internet in the
face of pervasive monitoring.  A workshop report in the form of
an IAB RFC will be produced after the event.

Technical questions for the workshop include:

- What are the pervasive monitoring threat models, and what is
  their effect on web and Internet protocol security and privacy?
- What is needed so that web developers can better consider the
  pervasive monitoring context?
- How are WebRTC and IoT impacted, and how can they be better
  protected? Are other key Internet and web technologies
  potentially impacted?
- What gaps exist in current tool sets and operational best
  practices that could address some of these potential impacts?
- What trade-offs exist between strengthening measures, (e.g.
  more encryption) and performance, operational or network
  management issues?
- How do we guard against pervasive monitoring while maintaining
  network manageability? 
- Can lower layer changes (e.g., to IPv6, LISP, MPLS) or
  additions to overlay networks help?
- How realistic is it to not be fingerprintable on the web and
  Internet?
- How can W3C, the IETF and the IRTF better deal with new
  cryptographic algorithm proposals in future?
- What are the practical benefits and limits of opportunistic
  encryption? 
- Can we deploy end-to-end crypto for email, SIP, the web, all
  TCP applications or other applications so that we mitigate
  pervasive monitoring usefully?
- How might pervasive monitoring take form or be addressed in
  embedded systems or different industrial verticals?
- How do we reconcile caching, proxies and other intermediaries
  with end-to-end encryption? 
- Can we obfuscate metadata with less overhead than TOR? 
- Considering meta-data: are there relevant differences between
  protocol artefacts, message sizes and patterns and payloads?

Position papers (maximum of 5 pages using 10pt font or any
length Internet-Drafts) from academia, industry and others that
focus on the broader picture and that warrant the kind of
extended discussion that a full day workshop offers are the most
welcome. Papers that reflect experience based on running code
and deployed services are also very welcome. Papers that are
proposals for point-solutions are less useful in this context,
and can simply be submitted as Internet-Drafts and discussed on
relevant IETF or W3C lists, e.g. the IETF perpass list. [3] 

The workshop will be by invitation only. Those wishing to attend
should submit a position paper or Internet-Draft.  All inputs
submitted and considered relevant will be published on the
workshop web page. The organisers (STREWS project participants,
IAB and W3C staff) will decide whom to invite based on the
submissions received.  Sessions will be organized according to
content, and not every accepted submission or invited attendee
will have an opportunity to present as the intent is to foster
discussion and not simply to have a sequence of presentations. 

[1] http://down.dsg.cs.tcd.ie/misc/perpass.txt
[2] http://www.strews.eu/
[3] https://www.ietf.org/mailman/listinfo/perpass