There was both the geopriv WG and the geojson WG. I would second Erik's
recommendation to contact the ART area on this type of work.
Regards,
Brian
On 1/20/20 4:01 PM, Erik Kline wrote:
> Rob,
>
> As you may well know there was once a working group (geopriv
>
[RFC3056] |
> | Allocation Date | February 2001 |
> | Termination Date | N/A |
> | Source | True |
> | Destination | True |
>
Bonica <rbon...@juniper.net>, Michelle Cotton
<michelle.cot...@icann.org>, Brian Haberman <br...@innovationslab.net>,
Leo Vegoda <leo.veg...@icann.org>, Ron Bonica <rbon...@juniper.net>,
Michelle S. Cotton <michelle.cot...@icann.org>
A new version of I-D, d
Bonica <rbon...@juniper.net>, Michelle Cotton
<michelle.cot...@icann.org>, Brian Haberman <br...@innovationslab.net>,
Leo Vegoda <leo.veg...@icann.org>, Ron Bonica <rbon...@juniper.net>,
Michelle S. Cotton <michelle.cot...@icann.org>
A new version of I-D, d
+--++
>
> Table 10: 6to4 Relay Anycast
>
> (One could debate the N/A but they are currently blank in the registry.)
>
> Regards
>Brian C
>
> On 16/08/2016 02:23, Brian Haberman wrote:
&
I am still looking for reviewers. It is generally an easy read.
Regards,
Brian
On 7/20/16 8:54 AM, Brian Haberman wrote:
> All,
> Last year, RFC 6890 was published as a mechanism for standardizing
> the information maintained in IANA's Special Use Address registries.
All,
Last year, RFC 6890 was published as a mechanism for standardizing
the information maintained in IANA's Special Use Address registries.
http://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml
All,
As per custom, we will be holding Internet AD office hours in
Buenos Aires. All three of us will be available on Wednesday from
1600-1700 in the Paraiso Room. Feel free to stop by and chat about
Internet Area issues that are of interest to you.
Regards,
Brian, Terry, & Suresh
esignating-rfcs-as-historic.html.
>
>
> Can you take care of creating a status-change document for these
> RFCs?
>
> Thank you.
>
> Cheers, Med
>
>> -Message d'origine- De : Int-area
>> [mailto:int-area-boun...@ietf.org] De la part de Brian Haberman
>> E
This is a fine thing to do, but it does not require an I-D to do it. An
AD can create a status-change document that moves the three RFCs
mentioned in the draft to Historic status. Any justification for the
move can be included in the status-change document. Here is an example
of one that was done
All,
This new mailing list may be of interest. It is hosting discussion
on deploying IP on very constrained wireless systems.
Regards,
Brian
Forwarded Message
Subject: New Non-WG Mailing List: lp-wan -- Low-Power Wide Area
Networking (LP-WAN), also known as LPWA or
All,
Apologies for the spam, but I think this is relevant to a number of
WGs. If you have an interest in the interactions between IP multicast
and 802.11 networks, please join the list and contribute to the discussion.
Regards,
Brian
Forwarded Message
Subject: New Non-WG
All,
Terry and I will be holding office hours in Yokohama. We have
scheduled the IESG breakout room (tentatively room 312) for 1300-1500 on
Wednesday. Feel free to stop by and chat about any INT area topic that
you have questions/comments/concerns about.
Regards,
Brian
signature.asc
All,
The INT ADs will be holding office hours during IETF 94. We will be
available during the 1300-1500 slot on Wednesday in the to-be-announced
IESG breakout room. Feel free to come by and chat about any INT
Area-related topics that are of interest to you.
Regards,
Brian & Terry
All,
I have mentioned this to a few people, but wanted to let the
community at-large know that I will not be standing for another term as
Internet AD. In short, I have found it to be a very rewarding
experience, but believe that 2 terms as an area director provides a good
balance between
Hi Kathleen,
On 5/14/15 9:49 PM, Ronald Bonica wrote:
Hi Kathleen,
Thanks, I will post an updated version of the draft.
Regarding Fred’s question, an attacker can send ICMP PTB to the GRE
ingress node. When this happens, the GRE ingress node’s estimation of
the PMTU and GMTU become
On 4/27/15 11:33 AM, Templin, Fred L wrote:
Hi Brian,
-Original Message-
From: Int-area [mailto:int-area-boun...@ietf.org] On Behalf Of Brian Haberman
Sent: Friday, April 24, 2015 2:39 PM
To: int-area@ietf.org
Subject: Re: [Int-area] I-D Action: draft-ietf-intarea-gre-ipv6-07.txt
On 4/24/15 3:04 PM, Ronald Bonica wrote:
Are we still on topic?
No.
signature.asc
Description: OpenPGP digital signature
___
Int-area mailing list
Int-area@ietf.org
https://www.ietf.org/mailman/listinfo/int-area
Fred,
On 4/9/15 2:12 PM, Templin, Fred L wrote:
Hi Brian,
I don't have plans of submitting a text proposal, but I have to say that this
document concerns me on many levels. It essentially says that there are
deployed implementations that do not honor the robustness principle
and then seeks
of tune and needs to be tuned. It
should not be an excuse to take the tunnel down unconditionally.
Thanks - Fred
fred.l.temp...@boeing.com
-Original Message-
From: Brian Haberman [mailto:br...@innovationslab.net]
Sent: Thursday, April 09, 2015 11:03 AM
To: Suresh Krishnan; Templin
Fred,
On 4/8/15 3:30 PM, Templin, Fred L wrote:
To be constructive, one way forward would be to define a new field in the GRE
header called the fragment field. It would be used to fragment the payload
packet prior to encapsulating each fragment in a separate delivery header.
This would be an
All,
If anyone is interested in helping a useful cause...
Regards,
Brian
Original Message
Subject: [ietf-privacy] old RFC reviews - please try this...
Date: Tue, 20 May 2014 10:23:34 +0100
From: Stephen Farrell stephen.farr...@cs.tcd.ie
To: ietf-priv...@ietf.org
All,
As with previous meetings, the INT ADs will be holding office hours
in London. We have scheduled our office hours for Thursday (Mar. 6th)
from 15:15 to 16:45. We will hold these in the yet-to-be-identified
IESG break-out room. There will be a follow-up e-mail once the room has
been
And to clarify, the time is 15:50 to 17:20 on Nov. 6th. I doubt we
could get through with just 30 minutes (as indicated the first time).
Regards,
Brian
On 10/25/13 3:13 PM, Brian Haberman wrote:
Just a reminder of the INT AD office hours. The IESG breakout room is
the Lord Byron room
All,
As with previous meetings, the INT ADs will be holding office hours
in Vancouver. We have scheduled our office hours for Wednesday (Nov.
6th) from 16:50 to 17:20. We will hold these in the
yet-to-be-identified IESG break-out room. There will be a follow-up
e-mail once the room has
All,
I have added Juan Carlos Zuniga as the third co-chair for the
int-area WG. I am looking forward to have Juan Carlos assist Suresh and
Julien in shepherding the work of the WG.
Welcome, JC!
Regards,
Brian
signature.asc
Description: OpenPGP digital signature
Suresh,
Sorry for the late feedback, but there are some issues that should
be discussed. Some of the following are my views of the document and
others are summarized based on feedback from others.
To be clear, the following comments are being made as an individual
participant.
1. The
The IESG breakout room has been identified. We will have office hours
from 1300 to 1500 on Monday (July 29th) in the Chess Room.
Regards,
Brian
On 7/11/13 1:22 PM, Brian Haberman wrote:
All,
As in the previous few meetings, the INT ADs will be holding
office hours in Berlin. We
All,
As in the previous few meetings, the INT ADs will be holding
office hours in Berlin. We will be available on Monday from 1300 to
1500 in the yet-to-be-identified IESG breakout room. Feel free to stop
by and ask questions or chat about any concerns/ideas you have about an
INT WG or
All,
I know I talked to a few of you during IETF 86 about mentoring.
Please consider volunteering. You do not need to be a greybeard to help
out...
Regards,
Brian
Original Message
Subject: IETF Mentor Program
Date: Mon, 01 Jul 2013 12:39:36 -0700
From: IETF Chair
On 2/28/13 10:34 AM, Brian Haberman wrote:
All,
Since the concept was well-received in Atlanta, we will be
repeating the AD office hours in Orlando. We will be available on
Monday from 1300 to 1500 in the yet-to-be-identified IESG breakout room.
Feel free to stop by and ask questions
All,
Since the concept was well-received in Atlanta, we will be
repeating the AD office hours in Orlando. We will be available on
Monday from 1300 to 1500 in the yet-to-be-identified IESG breakout room.
Feel free to stop by and ask questions or chat about any
concerns/ideas you have
Internet Area citizens,
In case you are interested in the IEEE OUI registry...
Regards,
Brian
Original Message
Subject: Re: [ieee-ietf-coord] FW: I-D Action:
draft-ieee-rac-oui-restructuring-00.txt
Date: Mon, 18 Feb 2013 15:15:11 +0100
From: Benoit Claise
On 2/12/13 5:34 AM, mohamed.boucad...@orange.com wrote:
Dear Brian,
Many thanks for the detailed review.
Please see inline.
Cheers, Med
-Message d'origine- De : int-area-boun...@ietf.org
[mailto:int-area-boun...@ietf.org] De la part de Brian Haberman
Envoyé : lundi 11 février 2013
On 2/13/13 1:16 AM, Suresh Krishnan wrote:
Hi Brian,
On 02/11/2013 07:44 PM, Brian Haberman wrote:
Hi Suresh,
On 2/11/13 7:08 PM, Suresh Krishnan wrote:
Hi Brian,
Thanks for the review. I wanted to clarify three points that you
raised and I will ask the authors take care of the rest
On 2/13/13 11:12 AM, mohamed.boucad...@orange.com wrote:
I would suggest re-ordering the table so that deployed approaches are
collected together (and labeling them as deployed). If the HTTP
Forwarded header is the only deployed approach, I would simply add a
note for the others stating
All,
I have completed my AD evaluation for the above draft and have
some feedback for the group. I will focus on the substantive comments
for the time being since some of them may result in re-written text in
places. I will follow up with the document authors on editorial nits
and such
Hi Suresh,
On 2/11/13 7:08 PM, Suresh Krishnan wrote:
Hi Brian,
Thanks for the review. I wanted to clarify three points that you
raised and I will ask the authors take care of the rest.
On 02/11/2013 04:11 PM, Brian Haberman wrote:
7. In Section 4.1.2, it would be good to describe any
All,
I have begun receiving summaries for the Atlanta IETF meeting.
They are available at :
http://trac.tools.ietf.org/area/int/trac/wiki/IETF85
Summaries will continue to be added to that page as they are received.
Any feedback, comments, or questions on these summaries are welcome.
Just a reminder of this opportunity. The IESG breakout room is room
202. Feel free to bring any ideas, issues, concerns, or questions.
Regards,
Brian Ralph
On 10/17/12 10:34 AM, Brian Haberman wrote:
All,
The INT ADs will be holding office hours on Thursday (Nov. 8) of
the IETF
All,
The INT ADs will be holding office hours on Thursday (Nov. 8) of
the IETF meeting from 1730-1900 in the IESG breakout room. Feel free to
stop by and chat about any INT Area issues that you have.
Regards,
Brian Ralph
___
Int-area mailing
Med,
My opinion, not as AD, is that this document should not make a
recommendation. This document should be strictly an analysis so that
we have a baseline understanding of all the existing solutions.
Brian
On 7/30/12 2:41 AM, mohamed.boucad...@orange.com wrote:
Dear Lars,
Could be
Hi Joe,
I have snipped the portions where no further discussion is needed...
On 5/7/12 4:35 PM, Joe Touch wrote:
* Section 4 : I am curious as to what impact you think this document
will have with trying to restrict the non-fragmentation use of the ID
field. With many of those types of
All,
I have performed the AD review for
draft-ietf-intarea-ipv4-id-update-04.txt. I have a few comments that I
would like addressed before this draft proceeds...
* Section 3 states that the IPv6 fragmentation header is only present
when a datagram has been fragmented. Section 5 of RFC
Dave,
Wasn't the comment made at the mike focused on having the class E
address space be used between the two layers of NAT?
Regards,
Brian
Dave Thaler wrote:
It's been pointed out several times in the past regarding class E
space that you cannot expect a host/app to work if you try to
45 matches
Mail list logo
