IETF Journal Volume 9 Issue 1

2013-07-24 Thread Matthew Ford
Hi,

The latest issue of the IETF Journal (Volume 9, Issue 1) is available online:

http://internetsociety.org/ietfjournal

Among many others it contains articles on software-defined networking, WebRTC 
and the Networking History BoF.

In addition you will find summary reports of the IETF 86 meeting held in 
Orlando, regular columns submitted by the IETF, the IAB and the IRTF chairs, 
summaries of the plenary sessions, and articles on the fellowships to IETF and 
the Applied Networking Research Prize.

You can read this publication online or download the full issue in PDF format. 
You can also keep up to date with the latest issue by subscribing to the IETF 
Journal as an email edition or have it delivered to your postal address in 
hardcopy.

Many thanks to all our contributors. Please send any comments or suggestions 
for future issues to ietfjour...@isoc.org.

Regards,
Mat

Mat Ford
Managing Editor
IETF Journal
http://internetsociety.org/ietfjournal

Reducing Internet Latency Workshop

2013-06-14 Thread Matthew Ford

Possibly of interest. (Short) Position paper deadline is 23rd June.

Regards,
Mat

Workshop on Reducing Internet Latency
=
25 - 26 September 2013
London, England

Latency tends to have been sacrificed in favour of headline bandwidth in the 
way the Internet has been built. This two-day invitation-only workshop aims to 
galvanise action to fix that. All layers of the stack are in scope.
Latency is an increasingly important topic for networking researchers and 
Internet practitioners alike. Data from Google, Microsoft, Amazon and others 
indicate that latency increases for interactive Web applications result in less 
usage and less revenue from sales or advertising income. Whether trying to 
provide platforms for Web applications, high-frequency stock trading, 
multi-player online gaming or 'cloud' services of any kind, latency is a 
critical factor in determining end-user satisfaction and the success of 
products in the marketplace. Consequently, latency and variation in latency are 
key performance metrics for services these days.

But latency reduction is not just about increasing revenues for big business. 
Matt Mullenweg of WordPress motivates work on latency reduction well when he 
says, "My theory here is when an interface is faster, you feel good. And 
ultimately what that comes down to is you feel in control. The [application] 
isn’t controlling me, I’m controlling it. Ultimately that feeling of control 
translates to happiness in everyone. In order to increase the happiness in the 
world, we all have to keep working on this."

Invitations to attend the workshop will depend on receipt of a position paper. 
In a spirit of co- ordination across the industry, submissions are encouraged 
from developers and network operators as well as the research and standards 
communities.

A wide range of latency related topics are in scope including, but not limited 
to:
- surveys of latency across all layers
- analyses of sources of latency and severity/variability
- the cost of latency problems to society and the economy, or the value of 
fixing it
- principles for latency reduction across the stack
- solutions to reduce latency, including cross-layer
- deployment considerations for latency reducing technology
- benchmarking, accreditation, measurement and market comparison practices

Submissions
---
This is an invitation-only workshop. Prospective participants must submit short 
(up to 2 pages) position papers outlining their views on a specific aspect of 
the overall scope. The emphasis here is on relevance and brevity - you do not 
need to write a lot of text, just demonstrate that you have thought about the 
problem space and have something interesting to say on the topic.

Please send position papers in PDF format to: late...@isoc.org

Participant numbers will be limited to focus on discussion and identifying 
actions rather than slideware.
Accepted position papers will be made public. A report on the workshop will be 
published after participants have agreed the content. Therefore, it will be 
possible to state views during the workshop without them being publicly 
attributed.

Important Dates
---
Position paper submission deadline: 23 June 2013
Paper acceptance notification: 28 June 2013
Workshop dates: 9am, Wednesday 25th – 5pm, Thursday 26th September 2013

Program committee
-
Mat Ford, Internet Society, co-chair
Bob Briscoe, BT, co-chair
Gorry Fairhurst, University of Aberdeen
Arvind Jain, Google
Jason Livingood, Comcast
Andrew McGregor, Google

Workshop venue and other details

Venue: Hilton London Paddington Hotel, 146 Praed Street, LONDON W2 1EE, UK
Registration fee: There is no registration fee for the workshop.
Recommended accommodation: Hilton London Paddington, registration link will be 
supplied to accepted participants.

The workshop is sponsored by the Internet Society, the RITE project, Simula 
Research Labs and the TimeIn project.
The Internet Society will host a workshop dinner on the Wednesday evening.

Re: ANRP 2013 - please nominate

2012-11-28 Thread Matthew Ford

On 28 Nov 2012, at 15:00, Matthew Ford  wrote:

> Hi,
> 
> Nominations for the 2013 ANRP awards are due by this Friday 30th November, so 
> if you've read a great paper this year, please send us the details using the 
> submission system at:
> 
>   http://irtf.org/anrp/2013/
> 
> or exceptionally, by email to a...@irtf.org.
> 
> Thanks,
> Mat


And, in case you are unfamiliar with the Applied Networking Research Prize 
(ANRP):

About the ANRP
--
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 IRTFresearch 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 
IRTFexperimentation, 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. In exceptional cases, 
nominations may also be submitted by email to a...@irtf.org.

All nominees will be notified by email about the decision regarding their 
nomination.

Nominations for the Applied Networking Research Prize (ANRP) are not considered 
to be contributions to the IETF. However, the invited talks at the IRTF Open 
Meeting are considered to be contributions, and the IRTF “Intellectual Property 
Rights” statement does apply to them.

ANRP 2013 - please nominate

2012-11-28 Thread Matthew Ford
Hi,

Nominations for the 2013 ANRP awards are due by this Friday 30th November, so 
if you've read a great paper this year, please send us the details using the 
submission system at:

http://irtf.org/anrp/2013/

or exceptionally, by email to a...@irtf.org.

Thanks,
Mat

IETF Journal - latest issue now available

2012-10-31 Thread Matthew Ford
Hi,

The latest issue of the IETF Journal (Volume 8, Issue 2) is available online:

http://internetsociety.org/ietfjournal

Among others it contains articles on the impact of World IPv6 Launch, using 
JSON in IETF protocols, software-defined networking, and moving toward a 
censorship-free Internet.

In addition you will find summary reports of the IETF 84 meeting held in 
Vancouver, regular columns submitted by the IETF, the IAB and the IRTF chairs, 
summaries of the plenary sessions, and articles on the fellowships to IETF.

You can read this publication online or download the full issue in PDF format. 
You can also keep up to date with the latest issue by subscribing to the IETF 
Journal as an email edition or have it delivered to your postal address in 
hardcopy.

Many thanks to all our contributors. Please send any comments or suggestions 
for future issues to ietfjour...@isoc.org.

Kind Regards,

Mat Ford
Managing Editor
IETF Journal
http://internetsociety.org/ietfjournal

Re: In Memoriam IETF web page

2012-10-23 Thread Matthew Ford

On 22 Oct 2012, at 21:48, Stephen Farrell  wrote:

> 
> 
> On 10/22/2012 03:52 PM, Henning Schulzrinne wrote:
>> If we want to keep this in the spirit of long-established (newspaper) 
>> traditions rather than a web page, we could use the IETF Journal for 
>> recording the passing of members of the community.
> 
> This sounds like the best suggestion to me so far
> if something is to be done. Second best would be
> to do nothing.
> 

In the last issue, we briefly noted the passing of Bob Morgan in the online 
version 
(http://www.internetsociety.org/articles/implementing-identity-management-solutions)
 though it was too late for the print issue. In the latest issue we've posted a 
tribute to Wendy Rickard 
(http://www.internetsociety.org/articles/remembering-wendy-rickard) both online 
and in print.

I think the IETF Journal is a fine place to publish obituaries or memorials of 
IETF contributors to recognise their work and I'd encourage anyone moved to 
write such text to send it to ietfjour...@isoc.org.

Mat




IETF Journal - latest issue now available

2012-07-24 Thread Matthew Ford
Hi,

The latest issue of the IETF Journal (Volume 8, Issue 1) is now available 
online at:

http://internetsociety.org/ietfjournal

Among others it contains articles on implementing identity management 
solutions, IPv6, and problems in low-delay communication.

In addition you will find summary reports of the IETF 83 meeting held in Paris, 
regular columns submitted by the IETF, the IAB and the IRTF chairs, summaries 
of the plenary sessions, and an article on the fellowship to IETF.

You can read this publication online or choose to download the full issue in 
PDF format. You can also keep up to date with the latest issue by subscribing 
to the IETF Journal as an email edition or have it delivered to your postal 
address in hardcopy.

Many thanks to all our contributors. Please send any comments or suggestions 
for future issues to ietfjour...@isoc.org.

Kind Regards,

Mat Ford
Managing Editor
IETF Journal
http://internetsociety.org/ietfjournal

IETF Journal v7.3 now available

2012-04-04 Thread Matthew Ford
Hi,

The new version of the IETF Journal (Volume 7, Issue 3) is now available online 
at
http://internetsociety.org/ietfjournal

Among others it contains articles on smart objects, data-centric networking and 
improvements to WHOIS. 

In addition to that you will find summary reports of the IETF 82 meeting, held 
in Taipei, regular columns submitted by the IETF, the IAB and the IRTF chairs, 
summaries of the plenary sessions, and an article on the fellowship to IETF.

You can read this publication online or choose to download the full issue in 
PDF format. You can also keep up to date with the latest issue by subscribing 
to the IETF Journal as an email edition or have it delivered to your postal 
address in hardcopy. Alternatively, you can subscribe to the RSS 2.0 news feed 
to have the latest issue delivered directly to your desktop as soon as it’s 
published.

Please send any comments or suggestions for future issues to 
ietfjour...@isoc.org.

Kind Regards,

Mat Ford
Managing Editor
IETF Journal
http://internetsociety.org/ietfjournal

Re: An Antitrust Policy for the IETF

2011-12-02 Thread Matthew Ford

On 1 Dec 2011, at 17:09, Worley, Dale R (Dale) wrote:

> Unfortunately, lawyers on the whole tend to
> suggest solutions to problems that create additional legal work.

… such as, an antitrust policy for the IETF...
___
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf


Latest IETF Journal (v6.3) - online now

2011-03-21 Thread Matthew Ford
[Apologies for duplicate emails]

Hello,

The new version of the IETF Journal (Volume 6, Issue 3) is now available online 
and for download at http://ietfjournal.isoc.org/

Among others it contains articles on the implications of mobile handheld 
devices for the Internet, the challenges of IPv4-IPv6 coexistence, and one 
regional registry's deployment of new routing security technology.

In addition to that you will find regular columns submitted by the IETF, IAB 
and IRTF chairs, and an article on the ISOC Fellowship to IETF 79.

You can read this publication online or choose to download the full issue in 
PDF format. You can also keep up to date with the latest issue of the IETF 
Journal by subscribing to one of our RSS or Atom feeds.

If you would like to receive hard copies of the IETF Journal for yourself or 
other chapter members, please contact us at ietfjour...@isoc.org. You can also 
send us any comments or suggestions you might have.

Kind Regards,

Mat Ford
Internet Society
http://isoc.org/
___
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf


Re: My comments to the press about RFC 2474

2010-09-07 Thread Matthew Ford
On 3 Sep 2010, at 21:13, Richard Bennett wrote:

> As Russ is now invoking your message to support his view that payment for 
> premium service is contrary to the wishes of IETF, that's a problem.
> 

No, it really isn't. That's not what Russ said.

Mat
___
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf


IETF Journal Volume 6 Issue 1 - now available

2010-06-28 Thread Matthew Ford
[Apologies for duplicate mails]

Hello,

The new issue of the IETF Journal - Volume 6, Issue 1 - is now available at 
http://ietfjournal.isoc.org/

Among others it contains articles on federated authentication, peer-to-peer 
developments, IPv6 momentum and the business of engineering successful Internet 
standards.

You can read this publication online or choose to download the full issue in 
PDF format. You can also keep up to date with the latest issue of the IETF 
Journal by subscribing to one of our RSS or Atom feeds.

For other comments or suggestions, please do not hesitate to contact us at 
ietfjour...@isoc.org.

Kind Regards,

Mat Ford
Internet Society
http://isoc.org/
___
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf


Re: IPv4 depletion makes CNN

2010-05-27 Thread Matthew Ford
On 27 May 2010, at 14:16, Ole Jacobsen wrote:

> 
> Is that the Matt Ford who works for ISOC or somebody else?
> 

The latter.


> The person quoted is well-known, so that makes me think this story was 
> written by someone with a clue.
> 

No comment ;)

Mat
___
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf


Re: [77attendees] FW: Looking for jogging trail around the Hilton)

2010-04-20 Thread Matthew Ford
I didn't get out of the hotel and off the treadmill in Anaheim, but I 
did get ietf-runners at ietf.org established.


Sign up today for the inside track on routes around Maastricht!

https://www.ietf.org/mailman/listinfo/ietf-runners

Mat


 Original Message 
Subject: Re: [77attendees] FW: Looking for jogging trail around the Hilton
Date: Tue, 23 Mar 2010 11:45:08 -0700
From: Vince Fuller 
To: Lindqvist Kurt Erik 
CC: 77attend...@ietf.org <77attend...@ietf.org>


> A wider view of Google maps shows that there is a bike trail along the
> Santa Ana river that is about 2.5 miles from the Hilton - south on
Harbor
> then east on Chapman would seem to be the most direct way to get to
that
> trail. When I asked the Hilton concierge about it, however, she
recommended
> against going there, saying that there have been many muggings on
the trail
> and that it isn't safe for running.

I ran there Saturday morning and it was full of people running and
biking, that was around 8.30. That was actually on recommendation
from the Hilton gym...


I ran this route this morning:

http://connect.garmin.com/activity/27834415

The trail wasn't particularly beautiful (the river is more of a flood
control
channel than a river) but it didn't seem unsafe and was more pleasant than
the roads around here. Not a lot of traffic on it on a weekday morning
but I
did see a few cyclists and a walker or two.

Less pleasant was running on Ball Road, which was wide, busy, and had no
sidewalk for a mile or so. I don't recommend running on that road.

--Vince
___
77attendees mailing list
77attend...@ietf.org
https://www.ietf.org/mailman/listinfo/77attendees

___
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf


Latest IETF Journal available now (Volume 5, Issue 3)

2010-01-29 Thread Matthew Ford

[Apologies for duplicate emails]

Hello,

The new issue of the IETF Journal - Volume 5, Issue 3 - is now
available at http://ietfjournal.isoc.org/

Among others it contains articles on Bandwidth on the Internet, the RFC 
Editor transition, Congestion Exposure and the Kantara Initiative.


You can read this publication online or choose to download the full
issue in PDF format. You can also keep up to date with the latest
issue of the IETF Journal by subscribing to one of our RSS or Atom
feeds.

For other comments or suggestions, please do not hesitate to contact us
at ietfjour...@isoc.org.

Kind Regards,

Mat Ford
Internet Society
http://isoc.org/
___
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf


Re: Proposed DNSSEC Plenary Experiment for IETF 74

2008-11-28 Thread Matthew Ford

On 28/11/08 09:44, Stephane Bortzmeyer wrote:

On Thu, Nov 27, 2008 at 07:49:13PM +,
 Matthew Ford <[EMAIL PROTECTED]> wrote 
 a message of 13 lines which said:



After all the years of FUD surrounding DNSSEC deployment, I feel
quite strongly that having the IETF do as you suggested and then be
able to point to 'no discernible impact' on the network would be a
significant milestone.


That would prove nothing: failures will DNSSEC do not happen every
day. Signatures expire, people stop signing without telling the parent
zone, keys rolls over, but it may not happen during these few days.

You see the actual problems with DNSSEC (which are *not* FUD) when you
run it every day, for several months. 


I said it would be a milestone. I didn't say it was the end of the road.

Mat

___
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf


Re: Proposed DNSSEC Plenary Experiment for IETF 74

2008-11-27 Thread Matthew Ford

On 27/11/08 19:36, David Conrad wrote:

 It's more that no one would notice.


After all the years of FUD surrounding DNSSEC deployment, I feel quite 
strongly that having the IETF do as you suggested and then be able to 
point to 'no discernible impact' on the network would be a significant 
milestone.


Mat
___
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf


Re: [73attendees] Is USA qualified for2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?

2008-11-18 Thread Matthew Ford

On 18/11/08 14:27, Soininen Jonne (NSN FI/Espoo) wrote:

Hi everybody,

In the IAOC, we have followed the visa situation for different nations
closely. It is obviously in the benefit for the IETF to have all the
participants that want and need to come to the IETF could also come.


Seems like the UK might offer a solution:

http://news.bbc.co.uk/1/hi/uk_politics/7736010.stm

"officials were "under pressure" to issue - rather than reject - visas 
to meet productivity targets."



___
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf


RE: IPv6 in the network, please

2004-11-10 Thread matthew . ford
So somebody needs to get Airespace's marketroids to slow down a little
bit:

http://www.airespace.com/news/press_releases/04_1026b.php

--Mat

P.S. Sincere thanks to the IETF61 NOC for making these efforts to get
IPv6 functional on the entire network - I'll try that new config now
from Lincoln.

On , [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]) wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Begin forwarded message:
> 
>> From: Ben Crosby <[EMAIL PROTECTED]>
>> Date: November 10, 2004 12:07:08 PM EST
>> To: [EMAIL PROTECTED]
>> Subject: IPv6
>> Reply-To: Ben Crosby <[EMAIL PROTECTED]>
>> 
>> Folks,
>> 
>>  To expand on Jeff's explanation of the IPv6 status here at
IETF61;
>> The entire network, both wired and wireless, was designed from the
>> get-go as being IPv6 capable. It also had a very real and major
>> requirement to be stable in the face of hundreds of clients all at
>> 100% transmit power, rogue APs,  and all the other problems that have
>> plagued previous IETF wireless networks. The good folks at Airespace
>> seemed to have a system that met this goal, and as we all can see,
>> it indeed works well. 
>> 
>>  However, when we asked Airespace to join us in this adventure,
it
>> became clear that the "intelligence" of their system worked through
>> tracking IPv4 DHCP requests, and thus wouldn't work with IPv6. This
>> lack of IPv6 support was nearly a show stopper, however Airespace
>> jumped through some major hoops to design, implement, and deploy code
>> that monitors RAs and RSs specifically to handle IPv6 for this
>> network. 
>> 
>>  Like most brand new code, when we deployed it, we encountered
>> problems. Problems that lead to instability in ALL wireless network
>> access. After several long days and nights of working on this long
>> before the first attendees arrived (we've been on site since Tuesday
>> 2nd - Election Day ;) we decided to disable the IPv6 support on the
>> wireless network, rather than risk the overall network stability.
>> Airespace continues to work on the problems, and we believe that we
>> have a reasonable interim solution.
>> 
>>  We have phased in a new image with limited deployment, which we
will
>> monitor. If we experience no problems, IPv6 will be back on the
>> wireless lan, however we need to maintain the overall stability of
>> the wireless network as our highest priority.
>> 
>>  For those who need IPv6 on wireless:
>> 
>>  SSID: ietf61v6
>>  WEP Key: thisisav6wlan
>>  Hex: 746869736973617636776c616e
>> 
>>  Coverage will be available in Georgetown, Lincoln, Jefferson,
>> Monroe, Military and Hemisphere. You should not associate with this
>> wireless network if you need stable IPv4. This is a dedicated
>> network with new AP's and a new controller. 
>> 
>>  My thanks to our volunteer staff who worked to deploy this
network
>> in the late hours last night (and very early hours this morning)
>> after the social event. 
>> 
>>  For those that are inconvenienced by the loss of IPv6, I
sincerely
>> apologize, and remind you that native IPv6 is available at every
>> wired port in the terminal room. 
>> 
>>  Thanks for bearing with us, and have a good meeting!
>> 
>>  - Ben Crosby
>>  Alcatel / IETF61 NOC
>> 
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.2.3 (Darwin)
> 
> iD8DBQFBklluLWqnmaznXfoRAi/qAJ4nUW48fV51MGYwRdX1IOqh2OAYHQCgvyZT
> nuUrX42hGaM8Xg7/fKPj1jc= =t7zw
> -END PGP SIGNATURE-
> 
> 
> ___
> Ietf mailing list
> [EMAIL PROTECTED]
> https://www1.ietf.org/mailman/listinfo/ietf

___
Ietf mailing list
[EMAIL PROTECTED]
https://www1.ietf.org/mailman/listinfo/ietf


RE: [IETF61] no IPv6?

2004-11-08 Thread matthew . ford
So we bounce around Abilene for a while:

>  1  2001:468:c12:128::4  5.709 ms  9.239 ms  7.733 ms
>  2  2001:468:c12:1::1  25.958 ms  7.548 ms  8.666 ms
>  3  2001:468:ff:185c::1  9.291 ms  6.951 ms  5.917 ms
>  4  atlang-washng.abilene.abilene.ucaid.edu  24.813 ms
> 30.656 ms  22.389 ms
>  5  hstnng-atlang.abilene.ucaid.edu  52.273 ms  44.055 ms *
>  6  losang-hstnng.abilene.ucaid.edu  84.828 ms  90.56 ms  74.04 ms

take a ride to Japan:

>  7  3ffe:8140:101:1::2  177.911 ms  187.557 ms  177.877 ms
>  8  hitachi1.otemachi.wide.ad.jp  177.499 ms  178.498 ms  179.06 ms
>  9  pc6.otemachi.wide.ad.jp  188.272 ms  188.571 ms  196.552 ms
> 10  3ffe:1800::3:2d0:b7ff:fe9a:6233  186.833 ms  187.182 ms 198.085 ms
> 11  3ffe:1800::3:230:48ff:fe41:4e95  194.045 ms  186.767 ms 186.333 ms

before winding up back where we started:

> 12  2001:468:ff:16c1::5  186.615 ms  194.852 ms  187.882 ms

So I conclude that IPv6 *is* deployed, but $DEITY help you if you need
to use it :)

-- Mat

> 13  v6-tunnel62-uk6x.ipv6.btexact.com  462.663 ms  458.041 ms  459.95
> ms 14  2001:800:40:2e02::1  517.889 ms  512.469 ms  515.928 ms
> 15  2001:800:40:2f02::2  520.688 ms  528.601 ms  513.428 ms
> 16  ns1.euro6ix.com  532.845 ms  519.352 ms  524.852 ms
> 
> Which was quite BAD !
> 
> But now I see:
> 
> Ordenador-de-Jordi-Palet:~ jordi$ traceroute6 www.6power.org connect:
> No route to host Ordenador-de-Jordi-Palet:~ jordi$ traceroute6
> www.6power.org connect: No route to host 
> 
> 
>> De: Stephane Bortzmeyer <[EMAIL PROTECTED]>
>> Responder a: [EMAIL PROTECTED]
>> Fecha: Mon, 8 Nov 2004 08:36:56 -0500
>> Para: Jun-ichiro itojun Hagino <[EMAIL PROTECTED]>
>> CC: [EMAIL PROTECTED]
>> Asunto: Re: [IETF61] no IPv6?
>> 
>> On Mon, Nov 08, 2004 at 01:41:00AM +0900,
>> Jun-ichiro itojun Hagino <[EMAIL PROTECTED]> wrote
>> a message of 9 lines which said:
>> 
>>> how come there's no IPv6 on the "IETF61" network?
>> 
>> Apparently, there is:
>> 
>> ~ % ifconfig eth0
>> eth0  Link encap:Ethernet  HWaddr 00:10:B5:49:F8:22
>> inet addr:130.129.67.235  Bcast:130.129.67.255
>> Mask:255.255.252.0 inet6 addr: fe80::210:b5ff:fe49:f822/64
>> Scope:Link inet6 addr: 2001:468:c12:64:210:b5ff:fe49:f822/64
>> Scope:Global ... 
>> 
>> ~ % traceroute6 www.iijlab.net
>> traceroute to sh1.iijlab.net
> (2001:240:0:200:260:97ff:fe07:69ea) from
>> 2001:468:c12:64:210:b5ff:fe49:f822, 30 hops max, 16 byte packets
>> 1  2001:468:c12:64::4 (2001:468:c12:64::4)  26.15 ms  0.924 ms 
>> 0.782 ms 2  2001:468:c12:1::1 (2001:468:c12:1::1)  14.643 ms  6.025
>> ms  5.321 ms 3  2001:468:ff:185c::1 (2001:468:ff:185c::1)  5.803 ms
>> 5.494 ms  6.086 ms 4  nycmng-washng.abilene.ucaid.edu
>> (2001:468:ff:1518::1) 29.869 ms  10.386 ms 
>> 37.157 ms
>> 5  chinng-nycmng.abilene.ucaid.edu (2001:468:ff:f15::1) 34.169 ms 
>> 43.274 ms 
>> 31.786 ms
>> ...
>> 
>> 
>> ___
>> Ietf mailing list
>> [EMAIL PROTECTED]
>> https://www1.ietf.org/mailman/listinfo/ietf
>> 
> 
> 
> 
> **
> Madrid 2003 Global IPv6 Summit
> Presentations and videos on line at:
> http://www.ipv6-es.com
> 
> This electronic message contains information which may be
> privileged or confidential. The information is intended to be
> for the use of the individual(s) named above. If you are not
> the intended recipient be aware that any disclosure, copying,
> distribution or use of the contents of this information,
> including attached files, is prohibited.
> 
> 
> 
> 
> ___
> Ietf mailing list
> [EMAIL PROTECTED]
> https://www1.ietf.org/mailman/listinfo/ietf

___
Ietf mailing list
[EMAIL PROTECTED]
https://www1.ietf.org/mailman/listinfo/ietf


Network 7

2003-06-18 Thread matthew . ford
Anyone know whether network 007/8 is 'IANA - Reserved' as IANA state here:
http://www.iana.org/assignments/ipv4-address-space or 'Allocated' as ARIN
state here:
ftp://ftp.arin.net/pub/stats/arin/arin.20030601?

Mat



RE: Financial state of the IETF - to be presented Wednesday

2003-03-17 Thread matthew . ford
I'm having quite a hard time seeing what the problem is here, but maybe I'm
missing something... Based on Harald's analysis the  projected annual
shortfall is in the region of $350,000 per annum. Assuming ~5,000 attendees
per annum, that equates to ~$70 per year per attendee. This equates to an
increase in fees of ~$25 per meeting, i.e. ~5.5%. Are there really any
regular attendees for whom this increase would constitute a serious problem?

Mat.



RE: ietf 55 network

2002-11-21 Thread matthew . ford
> folks have to tell the noc 
> about observed
> problems, rather than just complaining to your couch 
> neighbor.  

... and the noc has to help instead of telling people to go away. I
requested a static IP, was asked why I needed one, 'because DHCP is broken',
and was told that this was 'my problem'. Of course the reality is that DHCP
is always broken in some way, at some point, during IETF meetings, which is
why I always visit the NOC to request a static IP. This is the first time
I've been told 'no'.

I can't help thinking that the spastic wireless network experienced at
IETF55 could have been avoided if lessons learned at previous IETF meetings
had not been repeated. Maybe these lessons need to be captured somewhere.

I do appreciate the efforts of all the engineers who have been working hard
this week to give us the network that we now have, but on this occasion they
have left this user way less than satisfied.

Mat.