t == t p daedu...@btconnect.com writes:
t Just to make public what I have hinted at privately, I think that steps
t in section 4.1 may be somewhat underspecified.
t A related issue is that section 4.1 prefers DNS to DHCP for Kerberos
t information but the Security Considerations
Hello,
A message requesting guidance about getting pre-5378 signover was
sent to trust...@ietf.org on June 6. There hasn't been any response
from the IETF Trust.
Regards,
S. Moonesamy
- 'Basic Requirements for IPv6 Customer Edge Routers'
draft-ietf-v6ops-6204bis-09.txt as Informational RFC
this document persists in confusing routing and forwarding.
there are no routing protocols, a la 1812, here. there is confused text
such as
4.1. General Requirements
The IPv6 CE
Hi Ted,
On Jun 22, 2012, at 4:11 PM, Ted Lemon wrote:
On Jun 22, 2012, at 3:59 PM, Alissa Cooper wrote:
My understanding is that the option is encoded this way both for
extensibility and because the Valid-For parameter is solely a property of
the URI. Surely this is not the only instance
In message m2r4t0jx2l.wl%ra...@psg.com, Randy Bush writes:
- 'Basic Requirements for IPv6 Customer Edge Routers'
draft-ietf-v6ops-6204bis-09.txt as Informational RFC
this document persists in confusing routing and forwarding.
there are no routing protocols, a la 1812, here. there is
The IESG has received a request from the Web Authorization Protocol WG
(oauth) to consider the following document:
- 'An IETF URN Sub-Namespace for OAuth'
draft-ietf-oauth-urn-sub-ns-05.txt as Informational RFC
The IESG plans to make a decision in the next few weeks, and solicits
final
The IESG has received a request from the IPv6 over Low power WPAN WG
(6lowpan) to consider the following document:
- 'Transmission of IPv6 Packets over Bluetooth Low Energy'
draft-ietf-6lowpan-btle-08.txt as Proposed Standard
The IESG plans to make a decision in the next few weeks, and
The IESG has received a request from the DNS Extensions WG (dnsext) to
consider the following document:
- 'Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm
Implementation Status'
draft-ietf-dnsext-dnssec-algo-imp-status-03.txt as Best Current
Practice
The IESG plans to make a
The IESG has received a request from the DNS Extensions WG (dnsext) to
consider the following document:
- 'DNS Security (DNSSEC) DNSKEY Algorithm IANA Registry Updates'
draft-ietf-dnsext-dnssec-registry-update-03.txt as Proposed Standard
The IESG plans to make a decision in the next few weeks,
84th IETF Meeting
Vancouver, BC, Canada
July 29-August 3, 2012
Host: Google
Meeting venue: Hyatt Regency Vancouver http://Vancouver.hyatt.com
Register online at: http://www.ietf.org/meetings/84/
1. Registration
2. Visas Letters of Invitation
3. Bits-N-Bites Networking Event
4. Social Event
5.
The IESG has approved the following document:
- 'Resolution of The SPF and Sender ID Experiments'
(draft-ietf-spfbis-experiment-11.txt) as Informational RFC
This document is the product of the SPF Update Working Group.
The IESG contact persons are Pete Resnick and Barry Leiba.
A URL of this
The IESG has approved the following document:
- 'TRILL: Header Extension'
(draft-ietf-trill-rbridge-extension-05.txt) as Proposed Standard
This document is the product of the Transparent Interconnection of Lots
of Links Working Group.
The IESG contact persons are Ralph Droms and Brian
The IESG has received a request from the IPv6 Operations WG (v6ops) to
consider the following document:
- 'Basic Requirements for IPv6 Customer Edge Routers'
draft-ietf-v6ops-6204bis-09.txt as Informational RFC
The IESG plans to make a decision in the next few weeks, and solicits
final
13 matches
Mail list logo
