RUCUS Mailing List
The RUCUS mailing list is now live. You can subscribe here:
The RUCUS mailing list is now live. You can subscribe here:
The IESG has approved the RUCUS BoF, see the announcement here:
http://www.ietf.org/mail-archive/web/sipping/current/msg15014.html
A new mailing list is going to be setup and the BoF is being considered for the scheduling (hence no specific date is known yet).
I have also setup a new webpage for the BoF:
http://www.tschofenig.com/bof-rucus.html
It figured out that RUCUS is actually the name of a plant, namely this one:
There is still a lot of preparation work todo for the BoF and hence I would appreciate your feedback.
— Here is the announcement the US DOT recently posted. I am looking forward to see some feedback from these implementation and deployment efforts.
Progress continues in the US DOT Next Generation 9-1-1 Initiative. We
are pleased to announce the selection of PSAPs to participate in the
Proof of Concept (POC) portion of the project. The selected PSAPs are:
These PSAPs were selected from over 50 applicants, using objective
criteria developed by the NG9-1-1 team. While the field included many
impressive applicants, resulting in a very close competition, the
NG9-1-1 Initiative is limited by funding and schedule, requiring the
decision to limit participation. The US DOT sincerely acknowledges and
appreciates the willingness of all applicants to go “above and beyond”
in offering to participate in the POC.
The objective of this Proof of Concept is to test specific requirements,
selected from a prioritized list developed by the NG9-1-1 team with
input from a variety of 9-1-1 stakeholders. The requirements document,
along with all other documents produced by this project can be found on
the NG9-1-1 Web site. The NG9-1-1 POC is expected to begin in April 2008
and will last approximately three to six months. Following completion,
data gathered during the POC will be analyzed and used to revise the
system architecture and complete the transition plan.
The US DOT NG9-1-1 Initiative is an R&D project funded by the
Intelligent Transportation Joint Program Office. For further information
on the NG9-1-1 Initiative, go to http://www.its.dot.gov/ng911/index.htm.
In case you care about SIP and you would like to play around with some of the IETF protocols developed in the RAI area then you might want to look at the MSRPRelay page that recently went online.
Sieve is a language for filtering e-mail messages. The working group maintains a webpage that has recently been redesigned. It contains pointers to documents and implementations.
The W3C PLING group has just recently setup a Wiki for discussion about the policy language work. Currently, you can find the following information there:
Suresh wrote a nice little tool, called RFC Vision, for visualizing RFC relationships.
There is going to be another code sprint at the upcoming IETF meeting. Further information can be found here.
Saturday, 8 March 2008, begining at 9:30 AM
IETF Hotel in Philadelphia
A bunch of hackers get together to work on code for the IETF website. Some people may be porting of existing functionality to the new framework; some people may be adding exciting new functionality. All code will become part of the open source IETF tools.
If you plan to show up then you should really get the development environment, namely Django, working on your own machine. At the last event I had a couple of problems with my machine and lost of lot of time. Being familar with Python is obviously very useful…
You can find the position papers of the following persons on this mailing list:
A number of requests for BoFs have been submitted. You can track the status and a short summary here:
I have submitted a BoF request to form an Exploratory Group, an experiment introduced in RFC 5111. The main idea for this time-limited project is to work out the larger picture for dealing with unwanted communication attempts in SIP.
Here is the most recent BoF proposal description.
Last year Georgios Karagiannis, Ulrike Meyer and myself worked on an invited talk for the 1st IEEE Workshop on Enabling the Future Service-Oriented Internet (co-located with the GlobeComm 2007). The topic of our contribution On the Security of the Mobile IP Protocol Family. Ulrike gave the talk. I completely forgot the presentation; hence a little late but still up-to-date.
Let me know if you think it is useful. I might add audio to it.
Yesterday I gave my presentation at the 3rd ETSI Security Workshop. My presentation title was “IETF Security” and that is obviously pretty fuzzy. After looking on the agenda I decided that the most useful topic to speak about would be SIP identity management and media security. In case you are interested in this topic, please take a look at the following slide set.
Take a look at:
http://www.tschofenig.com/twiki/bin/view/KeyProv/KeyprovInterim2008
I restarted the roundup issue tracker again. It contains an updated list of issues that are going to be discussed during this face-to-face meeting.
After the IETF#70 GEOPRIV meeting a few of us had a chat about the conflicts we encountered in the group regarding the interpretation of RFC 3825. Here is a picture of the group participating in the chat:
I believe to have found the core problems:
Regarding the second question I have been chatting with a couple of guys working in the field of WLAN location determination and they told me that the way they work is to return a point with an uncertainty circle. Unfortunately, RFC 3825 does not return this information. Feedback on the second question is highly appreciated!
Another quite related question is whether there is deployment of RFC 3825 or whether folks are planning to deploy it. If there is no interest in doing it because everyone wants to go for, let’s say, LLDP-MED then still something needs to be done since LLDP-MED uses the RFC 3825 format. The situation would be different if people plan to use HELD or the OMA protocols.
Btw, we didn’t really come to a conclusion at the meeting.
IETF meetings are typically quite stressful; lots of presentations and lots of meetings. Here are some random pictures from the last IETF meeting.
For example, I met Dan York this IETF meeting.
On Wednesday evening we have our Working Group chairs beer evening.
Monday evening we have our Transport Area Directorate Dinner
We went to a place call “Blue Water Cafe”, see below:
…. and that’s the place inside:
The GEOPRIV meeting was on Friday (on the last day of the meeting). After the meeting Rohan Mahy was quite relaxed as you can see on this picture:
At the last IETF meeting (a while ago already) there was an interesting tutorial presentation about “Using XML in Internet Protocols”.
It is interesting to see that Tim is very much in favor of using Relax NG in IETF protocols. Whenever this discussion comes up then people tell me that XML schemas are so much better because of the tool support. Writing the specification for usage with Relax NG on the other hand is so much easier and also much easier to understand. In ECRIT, for example, we use Relax NG after the frustration we experienced in the GEOPRIV working group with the work on XML schemas.
The slides point also to RFC 3470 about “Guidelines for the Use of Extensible Markup Language (XML)”
– DATE
6 and 7 Feb 2008,
(8am - 6pm, both days)
– MEETING VENUE
RSA, The Security Division of EMC
174 Middlesex Turnpike
Bedford, MA 01730 —> approx 40-45 minute drive from Boston Logan
Airport
USA
– AGENDA
The meeting will focus on the discussion of the open issues of the three main working group documents:
Please find the latest information about the meeting here.
I will be at the 3rd ETSI Security Workshop next week.
In case you are interested please find the agenda here: http://portal.etsi.org/securityworkshop/Agenda08.asp
I am not yet sure what I am going to present. Still enough time…
Take a look at
http://www.rfc-editor.org/rfc/rfc5012.txt
http://www.rfc-editor.org/rfc/rfc5031.txt
http://www.rfc-editor.org/rfc/rfc5069.txt
Please find the DIME working group status update for January 2008 here:
http://www.tschofenig.com/twiki/bin/view/Dime/DimeStatusUpdate
Henning Schulzrinne found an interesting YouTube video related to emergency services:
In a recent posting Jeff Hodges wrote:
blogpost: (Draft) Technical Comparison: OpenID and SAML
document: Technical Comparison: OpenID and SAML - Draft 05
Abstract
This document presents a technical comparison of the OpenID Authentication
protocol and the Security Assertion Markup Language (SAML) Web Browser SSO Profile and the SAML framework itself. Topics addressed include design centers, terminology, specification set contents and scope, user identifier treatment, web single sign-on profiles, trust, security, identity provider discovery mechanisms, key agreement approaches, as well as message formats and protocol bindings. An executive summary targeting various audiences, and presented from the perspectives of end-users, implementors, tna deployers, is provided. We do not attempt to assign relative value between OpenID and SAML, e.g., which is “better”; rather, it attempts to present an objective technical comparison.
When you work on emergency services then you might be interested to submit a paper to the 2nd IEEE Workshop on Mission-Critical Networking (MCN’2008)
Important Dates:
Recently, I posted a link to a document about the Universal Service Directive. Alain Van Gaever wrote a slide set to explain what the changes actually mean.