NSIS and RSVP are protocols providing path-coupled signaling to interact with middleboxes along the path of a data flow. They follow the route of the data packets but do not influence routing of packets. NSIS was started as a follow-up activity of RSVP since the latter protocol suffers from a

New IETF Journal available now

The new issue of the IETF Journal – Volume 3, Issue 1 – is now available on http://ietfjournal.isoc.org This journal is quite valuable for those who would like to learn more about the current activities within the IETF. The most recent volume reports about “Routing and Addressing” at IETF#68.

DTNRG Meeting in Dublin

The DTNRG met on May 21st and 22nd 2007 in Dublin, Ireland.  A report was published and it contained a lot of security related information. In 2005 I attended a Dagstuhl workshop and shared my thoughts about security with the group.

New Media Security Requirements Document

We are getting close to the end with the media security requirements document. We have just published another version. The changes are small, namely: R27:   If SRTP keying is performed over the media path, the keying            packets MUST NOT pass the RTP validity check defined in           


RSVP is a path-coupled QoS signaling protocol. NSIS defines a follow-up version of RSVP offering more functionality, as described in a previous blog posting. At an IETF meeting I walked along the streets and found something really interesting — RSVP (Retired Senior Volunteer Patrol):

SPAM for Internet Telephony (SPIT) BOF

There might be a BOF on SPAM for Internet Telephony (SPIT) at the Chicago IETF meeting. Here are some of the documents I have been working on: Anti-SPIT : A Document Format for Expressing Anti-SPIT Authorization Policies Authorization Policies for Preventing SPIT SPAM for Internet Telephony (SPIT) Prevention using the

1 31 32 33 34 35 39