IETF Mail List Failure

[IETF Executive Director]

Dear IETF Community -

On 17 May, from 17:48 UTC (13:48 EDT) to 23:48 UTC (18:49 EDT), outbound email 
from the IETF email lists failed to send. Mail sent to the lists went into the 
archives, but was not received by list subscribers. 

A problem in the DMARC-rewriting system caused outbound mail delivery to fail 
silently, without alarm or error message. The rewriting system has been taken 
offline, which restored outbound email service.  The lists are back up.

Unfortunately, because the mail was discarded rather than queued, if you sent 
mail to any IETF list today during the outage window, we ask you to please 
resend your message.

We apologize for this issue and are working with the Tools Team to correct the 
system before it is put back online again.

Alexa Morris
IETF Executive Director

RFC 8375 on Special-Use Domain 'home.arpa.'

[rfc-editor]

A new Request for Comments is now available in online RFC libraries.


RFC 8375

Title:  Special-Use Domain 'home.arpa.' 
Author: P. Pfister, 
T. Lemon
Status: Standards Track
Stream: IETF
Date:   May 2018
Mailbox:pierre.pfis...@darou.fr, 
mel...@fugue.com
Pages:  12
Characters: 27377
Updates:RFC 7788

I-D Tag:draft-ietf-homenet-dot-14.txt

URL:https://www.rfc-editor.org/info/rfc8375

DOI:10.17487/RFC8375

This document specifies the behavior that is expected from the Domain
Name System with regard to DNS queries for names ending with
'.home.arpa.' and designates this domain as a special-use domain
name. 'home.arpa.' is designated for non-unique use in residential
home networks.  The Home Networking Control Protocol (HNCP) is
updated to use the 'home.arpa.' domain instead of '.home'.

This document is a product of the Home Networking Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-edi...@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC

Formal IESG Teleconference WebEx and Dial-in Information: 24 May 2018

[IESG Secretary]

As previously announced [1], all members of the community are welcome to 
attend formal IESG telechats as observers.

The next formal IESG telechat will be held on Thursday, May 24, 
2018 at 07:00 PT (14:00 UTC).  WebEx and Dial-in information is at the bottom 
of this message.

The agenda for the upcoming telechat can be found at


A calendar of upcoming public telechats can be downloaded or subscribed 
to at: 
https://www.ietf.org/calendars/iesg/iesgpublic.ics


Topic: IESG Formal Telechat
Date: Thursday, May 24, 2018
Time: 07:00 PDT (San Francisco, UTC-07:00)
09:00 CDT
10:00 EDT
14:00 UTC
15:00 United Kingdom
16:00 Germany, France, Switzerland
17:00 Finland
00:00 (next day) Australia (Queensland)


--- 
JOIN WEBEX MEETING
https://ietf.webex.com/ietf/j.php?MTID=m343b1173b6e1ed21d30db16ee0202473
Meeting number: 642 944 708
Meeting password: 1234


JOIN BY PHONE
1-650-479-3208 Call-in toll number (US/Canada)
Access code: 642 944 708
--- 
To join the audio conference using Skype 
--- 
1.  Bring up your Skype application.
2.  Bring up your browser, and go to the WebEx URL.
3.  Enter your name and email address.
4.  Close the WebEx window prompting for a phone number.
5.  Select the "info" tab at the top of the WebEx browser page.
6.  Go to Skype, and dial the U.S. Toll-Free number from the meeting 
announcement.
7.  Click on the DialPad tab on the Skype window.
8.  Use the virtual keypad to enter the meeting number followed by #.
9.  Use the virtual keypad to enter your attendee ID followed by #.

The playback of UCF (Universal Communications Format) rich media files
requires appropriate players. To view this type of rich media files in
the meeting, please check whether you have the players installed on your
computer by going to https://workgreen.webex.com/workgreen/
systemdiagnosis.php.

Sign up for a free trial of WebEx
http://www.webex.com/go/mcemfreetrial

http://www.webex.com

CCP:+14087926300x960506070#

IMPORTANT NOTICE: This WebEx service includes a feature that allows
audio and any documents and other materials exchanged or viewed during
the session to be recorded. By joining this session, you automatically
consent to such recordings. If you do not consent to the recording,
discuss your concerns with the meeting host prior to the start of the
recording or do not join the session. Please note that any such
recordings may be subject to discovery in the event of litigation.

[1] 
https://mailarchive.ietf.org/arch/msg/ietf-announce/Eackc8-MgJw8IbdquLuPlcoDZpo

RFC 8388 on Usage and Applicability of BGP MPLS-Based Ethernet VPN

[rfc-editor]

A new Request for Comments is now available in online RFC libraries.


RFC 8388

Title:  Usage and Applicability of BGP 
MPLS-Based Ethernet VPN 
Author: J. Rabadan, Ed.,
S. Palislamovic,
W. Henderickx,
A. Sajassi,
J. Uttaro
Status: Informational
Stream: IETF
Date:   May 2018
Mailbox:jorge.raba...@nokia.com, 
senad.palislamo...@nokia.com, 
wim.henderi...@nokia.com,
saja...@cisco.com, 
utt...@att.com
Pages:  31
Characters: 76431
Updates/Obsoletes/SeeAlso:   None

I-D Tag:draft-ietf-bess-evpn-usage-09.txt

URL:https://www.rfc-editor.org/info/rfc8388

DOI:10.17487/RFC8388

This document discusses the usage and applicability of BGP MPLS-based
Ethernet VPN (EVPN) in a simple and fairly common deployment
scenario.  The different EVPN procedures are explained in the example
scenario along with the benefits and trade-offs of each option.  This
document is intended to provide a simplified guide for the deployment
of EVPN networks.

This document is a product of the BGP Enabled Services Working Group of the 
IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-edi...@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC

RFC 8386 on Privacy Considerations for Protocols Relying on IP Broadcast or Multicast

[rfc-editor]

A new Request for Comments is now available in online RFC libraries.


RFC 8386

Title:  Privacy Considerations for Protocols Relying 
on IP Broadcast or Multicast 
Author: R. Winter, 
M. Faath,
F. Weisshaar
Status: Informational
Stream: IETF
Date:   May 2018
Mailbox:rolf.win...@hs-augsburg.de, 
fa...@conntac.net, 
fabian.weissh...@hs-augsburg.de
Pages:  13
Characters: 32238
Updates/Obsoletes/SeeAlso:   None

I-D Tag:draft-ietf-intarea-broadcast-consider-09.txt

URL:https://www.rfc-editor.org/info/rfc8386

DOI:10.17487/RFC8386

A number of application-layer protocols make use of IP broadcast or
multicast messages for functions such as local service discovery or
name resolution.  Some of these functions can only be implemented
efficiently using such mechanisms.  When using broadcast or multicast
messages, a passive observer in the same broadcast or multicast
domain can trivially record these messages and analyze their content.
Therefore, designers of protocols that make use of broadcast or
multicast messages need to take special care when designing their
protocols.

This document is a product of the Internet Area Working Group Working Group of 
the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-edi...@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC

IETF 102 Social Event Tickets On Sale!

[IETF Secretariat]

IETF 102
Montreal
July 14-20, 2018
Host: Juniper Networks

Social Event tickets are now available for purchase!

Date: Tuesday, 17 July, 2018
Time: 19:00 - 22:00
Cost: $35 USD per ticket, limit two per attendee. 
Hosted by: Juniper
Location: 1909 Taverne Moderne

Link to purchase tickets: 
https://www.ietf.org/registration/ietf102/eventticket.py

More information here: https://ietf.org/how/meetings/102/social/

Join us at 1909 Taverne Moderne for your IETF 102 social reception hosted by 
Juniper Networks! Just a short walk from Fairmont the Queen Elizabeth Hotel, 
you'll enjoy delicious food, craft beer, networking, and entertainment from 
7:00pm-10:00pm.