Rob Austein | 4 Mar 2007 01:00
Favicon

Weekly posting summary for ipv6 <at> ietf.org

    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 25.00% |    1 | 28.30% |     5109 | soohong.park <at> samsung.com
 25.00% |    1 | 26.12% |     4714 | alexandru.petrescu <at> motorola.com
 25.00% |    1 | 25.86% |     4668 | mailman-owner <at> ietf.org
 25.00% |    1 | 19.72% |     3559 | sra+ipng <at> hactrn.net
--------+------+--------+----------+------------------------
100.00% |    4 |100.00% |    18050 | Total

Grunchweather Associates provides this automatic summary on an at-whim
basis at the request of the IPv6 WG chairs.  Your mileage may vary.
We decline responsibilities, all shapes, all sizes, all colors.
If this script produces broken output, you get to keep both pieces.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6 <at> ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

Praburaajan | 5 Mar 2007 12:46

HITBSecConf2007 - Malaysia: Call for Papers now Open

The CFP for HITBSecConf2007 - Malaysia is now open. HITBSecConf -
Malaysia is the premier network security event for the region and the
largest gathering of hackers in Asia. Our 2007 event is expected to
attract over 700 attendees from around the world and will see 4 keynote
speakers in addition to 40 deep-knowledge technical researchers
presenting over two-days.

Being a deep-knowledge technical conference, talks that are more
technical or that discuss new and never before seen attack methods are
of more interest than a subject that has been covered several times
before. Summaries not exceeding 250 words should be submitted (in plain
text format) to cfp <at> hackinthebox.org for review and possible inclusion
in the programme.

Submissions are due no later than 1st May 2007.

Topics of interest include, but are not limited to the following:

# 3G/4G Cellular Networks
# SS7/Backbone telephony networks
# Analysis of network and security vulnerabilities
# Firewall technologies
# Intrusion detection
# Data Recovery and Incident Response
# GPRS and CDMA Security
# Identification and Entity Authentication
# Network Protocol and Analysis
# Smart Card Security
# Virus and Worms
# WLAN and Bluetooth Security
(Continue reading)

Brian E Carpenter | 5 Mar 2007 17:21
Picon
Favicon

Re: I-D ACTION:draft-arifumi-ipv6-rfc3484-revise-00.txt

> 2.4.  To make address type dependent control possible
...
>    For example, You can set priority on RFC 3041 [RFC3041] address by
>    putting a line in policy table specifying RFC 3041 address by 128-bit
>    prefixlen and continuing to update policy table according to RFC 3041
>    address re-generation.  But, this is surely troublesome for users and
>    implementers.

I'm not sure I understand what this means. Can give a more detailed
example?

...
>    To prefer privacy address by default, and to prefer RA-generated
>    address for site internal, the policy table will look like this.
> 
>            Prefix                         Pref   Label
>            2001:db8:1234::(PRIVACY)/128   30     2
>            ::/0                           10     2
>            2001:db8:1234::(RA):/128       30     1
>            2001:db8::/48                  20     1

Does this mean that (PRIVACY) and (RA) will be literally in
the table or does it stand for something else?

    Brian

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6 <at> ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
(Continue reading)

skalli yassir | 6 Mar 2007 21:37
Picon

a fixed ipv6 address

hi
i'm a beginner in the ipv6  protocole and i have a problem  with the ipv6 address
when i give an adress to my interface either with ifconfig or with the file of configuration 
before restarting the interface that's ok but when i restart it,  that  has no effect;
please can some one give a solution in order to have a fixed ipv6 address( local link)
:)
thanks

--
Scales of success are not easy to be ridden

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6 <at> ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
skalli yassir | 7 Mar 2007 00:55
Picon

Re: a fixed ipv6 address

hi,
yes i have this problem just in linux
----that is what i use to assign the address

ifconfig etho add 3FFE:302:CAFE::2
or i modify the file  (/etc/sysconfig/network) i add the line 

IPV6_AUTOCONF=yes

in the file  /etc/sysconfig/network-scripts/ifcfg-eth0 i add

IPV6INIT=yes

IPV6ADDR=3FFE:302:CAFE::2

can you tell me another way to assign a fixed address

best regards;
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6 <at> ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
Arifumi Matsumoto | 7 Mar 2007 12:03

Re: Fwd: I-D ACTION:draft-arifumi-ipv6-rfc3484-revise-00.txt

Brian,
thank you for your comments.

Firstly, let me announce my I-D draft that summarizes the discussion
we had at this ML long long ago.
http://www1.ietf.org/mail-archive/web/i-d-announce/current/msg14135.html

I welcome every comment. Now, I'm having a trouble finding a place for my I-D,
because intarea is for RAM this time at 68th IETF. :(

Comments below.

> From: Brian E Carpenter <brc <at> zurich.ibm.com>
> Date: 2007/03/06 1:21
> Subject: Re: I-D ACTION:draft-arifumi-ipv6-rfc3484-revise-00.txt
> To: IPv6 <ipv6 <at> ietf.org>
> 
> 
>> 2.4.  To make address type dependent control possible
> ...
>>    For example, You can set priority on RFC 3041 [RFC3041] address by
>>    putting a line in policy table specifying RFC 3041 address by 128-bit
>>    prefixlen and continuing to update policy table according to RFC 3041
>>    address re-generation.  But, this is surely troublesome for users and
>>    implementers.
> 
> I'm not sure I understand what this means. Can give a more detailed
> example?

I feel sorry for my poor description.
For example, if you use a RFC 3041 address "2001:db8:1234::1:2:3:4",
you can configure when to use RFC 3041 address and when not to use it
by using the following policy table.

            Prefix                         Pref   Label
            2001:db8:1234::1:2:3:4         30     2
            ::/0                           10     2
            2001:db8:1234::a               30     1
            2001:db8::/48                  20     1

However, RFC 3041 address changes frequently. So you have to configure
your policy table accordingly every time RFC 3041 address changes.

            Prefix                         Pref   Label
            2001:db8:1234::5:6:7:8         30     2      <-- change
            ::/0                           10     2
            2001:db8:1234::a               30     1
            2001:db8::/48                  20     1

Briefly, if you want to use finer grained control(not just on-off switch)
of RFC 3041 address, you can use policy table by stating 128 bit of your
RFC 3041 address and keeping track of address changes.

> 
> ...
>>    To prefer privacy address by default, and to prefer RA-generated
>>    address for site internal, the policy table will look like this.
>>
>>            Prefix                         Pref   Label
>>            2001:db8:1234::(PRIVACY)/128   30     2
>>            ::/0                           10     2
>>            2001:db8:1234::(RA):/128       30     1
>>            2001:db8::/48                  20     1
> 
> Does this mean that (PRIVACY) and (RA) will be literally in
> the table or does it stand for something else?

The system, usually OS kernel, knows the attributes of each address that
the system possesses. That is, which is RA-generated address, which is
RFC 3041 address, which is manually assigned address and which is 
DHCP-based address.

Our motivation is to make it possible for users or site administrators
to achieve address attribute dependent address selection. So, I don't
stick to how this is implemented, macro or flag. What's important is that
there should be any measure for users to tell the system which kind of
address they want to use for a specific destination.

I received a related question from Tim Chown at v6ops ML on 19 Feb.
I hope this helps.

Best regards.

--

-- 
Arifumi Matsumoto
    IP Technology Expert Team
    Secure Communication Project
    NTT Information Sharing Platform Laboratories
    E-mail: arifumi <at> nttv6.net

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6 <at> ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

Internet-Drafts | 9 Mar 2007 21:50
Picon
Favicon

I-D ACTION:draft-ietf-ipv6-2461bis-11.txt

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the IP Version 6 Working Group Working Group of the IETF.

	Title		: Neighbor Discovery for IP version 6 (IPv6)
	Author(s)	: T. Narten, et al.
	Filename	: draft-ietf-ipv6-2461bis-11.txt
	Pages		: 88
	Date		: 2007-3-9
	
This document specifies the Neighbor Discovery protocol for IP
   Version 6.  IPv6 nodes on the same link use Neighbor Discovery to
   discover each other's presence, to determine each other's link-layer
   addresses, to find routers and to maintain reachability information
   about the paths to active neighbors.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ipv6-2461bis-11.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request <at> ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-ipv6-2461bis-11.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv <at> ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-ipv6-2461bis-11.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
Attachment: message/external-body, 135 bytes
Attachment (draft-ietf-ipv6-2461bis-11.txt): message/external-body, 68 bytes
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6 <at> ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
Rob Austein | 11 Mar 2007 01:00
Favicon

Weekly posting summary for ipv6 <at> ietf.org

    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 28.57% |    2 | 31.03% |    12615 | skalliyassir <at> gmail.com
 14.29% |    1 | 16.86% |     6856 | arifumi <at> nttv6.net
 14.29% |    1 | 16.53% |     6719 | internet-drafts <at> ietf.org
 14.29% |    1 | 13.79% |     5606 | prabu <at> hackinthebox.org
 14.29% |    1 | 12.57% |     5111 | brc <at> zurich.ibm.com
 14.29% |    1 |  9.22% |     3750 | sra+ipng <at> hactrn.net
--------+------+--------+----------+------------------------
100.00% |    7 |100.00% |    40657 | Total

Grunchweather Associates provides this automatic summary on an at-whim
basis at the request of the IPv6 WG chairs.  Your mileage may vary.
We decline responsibilities, all shapes, all sizes, all colors.
If this script produces broken output, you get to keep both pieces.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6 <at> ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

Tsuneaki Takeda | 11 Mar 2007 03:23
Picon

A typo on MinRtrAdvInterval in 2461bis-11

Hi all,

In the section 6.2.1, <draft-ietf-ipv6-2461bis-11.txt> has the
following definition: 

 | MinRtrAdvInterval
 |                   The minimum time allowed between sending
 |                   unsolicited multicast Router Advertisements from
 |                   the interface, in seconds. MUST be no less than 3
 |                   seconds and no greater than .75 *
 |                   MaxRtrAdvInterval.
 |
 |                   Default: 0.33 * MaxRtrAdvInterval
 |                   If MaxRtrAdvInterval >= 9 seconds, otherwise the
 |                   Default is MaxRtrAdvInterval.

The formula defining the default value of MinRtrAdvInterval is
strange. This should be a typo.  Its intention, I guess, is

             if MaxRtrAdvInterval >=9,  
                        Default:  0.33 * MaxRtrAdvInterval, 
             otherwise(if 4 =< MaxRtrAdvInterval < 9),
                        Default:  3

Regards

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6 <at> ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

Julien Laganier | 12 Mar 2007 10:31
Favicon

Fwd: I-D ACTION:draft-chakrabarti-ipv6-addrselect-api-05.txt

Folks,

An updated version of the IPv6 address selection API 
draft has been published (see below). Over the years, 
this draft has been reviewed by many participants to 
the IPv6 WG, and has been supported by many of them. 
Their feedback has been incorporated in successive 
revision of the draft. There are also serious 
implementers waiting for this draft to be published.

Therefore, we'd like this draft to be published as an 
Informational RFC.

What do you think?

Best,

--julien

-------------------------------------------------------------
A New Internet-Draft is available from the on-line 
Internet-Drafts 
directories.

	Title		: IPv6 Socket API for Address Selection
	Author(s)	: E. Nordmark, et al.
	Filename	: 
draft-chakrabarti-ipv6-addrselect-api-05.txt
	Pages		: 34
	Date		: 2007-3-7
	
The IPv6 default address selection document [RFC3484] 
describes the
   rules for selecting source and destination IPv6 
addresses, and
   indicates that applications should be able to 
reverse the sense of
   some of the address selection rules through some 
unspecified API.
   However, no such socket API exists in the basic 
[RFC3493] or advanced
   [RFC3542] IPv6 socket API documents.  This document 
fills that gap by
   specifying new socket level options and flags for 
the getaddrinfo()
   API to specify preferences for address selection 
that modify the
   default address selection algorithm.  The socket API 
described in
   this document will be particularly useful for IPv6 
applications that
   want to choose between temporary and public 
addresses, and for Mobile
   IPv6 aware applications that want to use the care-of 
address for
   communication.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-chakrabarti-ipv6-addrselect-api-05.txt

To remove yourself from the I-D Announcement list, send 
a message to 
i-d-announce-request <at> ietf.org with the word unsubscribe 
in the body of 
the message. 
You can also visit 
https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. 
Login with the 
username "anonymous" and a password of your e-mail 
address. After 
logging in, type "cd internet-drafts" and then 
"get draft-chakrabarti-ipv6-addrselect-api-05.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv <at> ietf.org.
In the body type:
	"FILE /internet-drafts/draft-chakrabarti-ipv6-addrselect-api-05.txt".
	
NOTE:	The mail server at ietf.org can return the 
document in
	MIME-encoded form by using the "mpack" utility.  To 
use this
	feature, insert the command "ENCODING mime" before the 
"FILE"
	command.  To decode the response(s), you will need 
"munpack" or
	a MIME-compliant mail reader.  Different 
MIME-compliant mail readers
	exhibit different behavior, especially when dealing 
with
	"multipart" MIME messages (i.e. documents which have 
been split
	up into multiple messages), so check your local 
documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant 
mail reader
implementation to automatically retrieve the ASCII 
version of the
Internet-Draft.
Picon Favicon
From: Folks, An updated version of the IPv6 address selection API draft has been published (see below). Over the years, this draft has been reviewed by many participants to the IPv6 WG, and has been supported by many of them. Their feedback has been incorporated in successive revision of the draft. There are also serious implementers waiting for this draft to be published. Therefore, we'd like this draft to be published as an Informational RFC. What do you think? Best, --julien ------------------------------------------------------------- A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : IPv6 Socket API for Address Selection Author(s) : E. Nordmark, et al. Filename : draft-chakrabarti-ipv6-addrselect-api-05.txt Pages : 34 Date : 2007-3-7 The IPv6 default address selection document [RFC3484] describes the rules for selecting source and destination IPv6 addresses, and indicates that applications should be able to reverse the sense of some of the address selection rules through some unspecified API. However, no such socket API exists in the basic [RFC3493] or advanced [RFC3542] IPv6 socket API documents. This document fills that gap by specifying new socket level options and flags for the getaddrinfo() API to specify preferences for address selection that modify the default address selection algorithm. The socket API described in this document will be particularly useful for IPv6 applications that want to choose between temporary and public addresses, and for Mobile IPv6 aware applications that want to use the care-of address for communication. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-chakrabarti-ipv6-addrselect-api-05.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request <at> ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-chakrabarti-ipv6-addrselect-api-05.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv <at> ietf.org. In the body type: "FILE /internet-drafts/draft-chakrabarti-ipv6-addrselect-api-05.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. <Internet-Drafts <at> ietf.org>
Subject: I-D ACTION:draft-chakrabarti-ipv6-addrselect-api-05.txt
Date: 2007-03-07 20:50:02 GMT
A New Internet-Draft is available from the on-line Internet-Drafts 
directories.

	Title		: IPv6 Socket API for Address Selection
	Author(s)	: E. Nordmark, et al.
	Filename	: draft-chakrabarti-ipv6-addrselect-api-05.txt
	Pages		: 34
	Date		: 2007-3-7
	
The IPv6 default address selection document [RFC3484] describes the
   rules for selecting source and destination IPv6 addresses, and
   indicates that applications should be able to reverse the sense of
   some of the address selection rules through some unspecified API.
   However, no such socket API exists in the basic [RFC3493] or advanced
   [RFC3542] IPv6 socket API documents.  This document fills that gap by
   specifying new socket level options and flags for the getaddrinfo()
   API to specify preferences for address selection that modify the
   default address selection algorithm.  The socket API described in
   this document will be particularly useful for IPv6 applications that
   want to choose between temporary and public addresses, and for Mobile
   IPv6 aware applications that want to use the care-of address for
   communication.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-chakrabarti-ipv6-addrselect-api-05.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request <at> ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-chakrabarti-ipv6-addrselect-api-05.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv <at> ietf.org.
In the body type:
	"FILE /internet-drafts/draft-chakrabarti-ipv6-addrselect-api-05.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
Attachment: message/external-body, 149 bytes
_______________________________________________
I-D-Announce mailing list
I-D-Announce <at> ietf.org
https://www1.ietf.org/mailman/listinfo/i-d-announce
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6 <at> ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

Gmane