Re: [16NG] Re: suggest separation of IPv4 from document (was: I-DACTION:draft-ietf-16ng-ip-over-ethernet-over-802.16-00.txt)

[Alexandru Petrescu <[e-mail]>]

Riegel, Maximilian wrote:
> There is reason to keep both versions in one document. As you can 
> figure out, most of the document applies to both IPv4 as well as IPv6
>  and only small parts are IP version specific. This will become more 
> visible when we are fully leveraging RFC4541 for IPv6 transmission in
>  the next version. And even in the combined version the ducument is 
> very handy; less than 20 pages do not qualify a split.

Maximilian, thanks for the email.

If you think there is reason to keep both versions in one document, and
your co-authors too and the WG too - then I'm fine.

I do not know of any other IP over foo document that treats both IPv4
and IPv6.  This may be the first one.  I think it can be too complex,
but I will not insist on this.

> The I-D does not intend to replace RFC2464 or RFC894 but provides 
> 'lower layer' additions to make Ethernet over 802.16 looking like 
> standard Ethernet to the IP layer, even when not all messages are 
> going over the air like in 'plain' Ethernet.

I think this is lower layer additions that are not IP, and that should
be suggested to IEEE, not at IETF.  I mean, a ND Relay only pertains to
802.16.  And so I think it should be part of IEEE, or at most
informational track at IETF.

Do you see any other link using ND Relay?  (other than 802.16)?

Thanks,

Alex

> 
> 
> Bye Max
> 
> -----Original Message----- From: Alexandru Petrescu 
> [mailto:[e-mail]] Sent: Friday, December 15, 
> 2006 3:06 PM To: [e-mail] Subject: [16NG] Re: suggest separation
>  of IPv4 from document (was: 
> I-DACTION:draft-ietf-16ng-ip-over-ethernet-over-802.16-00.txt)
> 
> Also, I would like to suggest separation of the IPv4 section 8.1 
> "IPv4 over Ethernet" from the document, and title the document "IPv6 
> over...".
> 
> The reason is simple - simplicity, easier to deal with shorter 
> documents.
> 
> For example, the current section 8.1 suggests that it is sufficient 
> to implement IPv4 over 802.16 ETH CS by looking at RFC 894 and RFC 
> 826 (IPv4 over Ethernet and ARP specs, respectively).
> 
> However, when writing an implementation of IPv4 over ETH CS an 
> important parameter is the Ether type.  For IPv6 it's simple - it's 
> 0x86DD for _all_ IPv6, ND included, spec'd in rfc2464.  But for IPv4 
> it's 0x800 (spec'ed in rfc894) and ARP it's 0x806.  This latter 
> figure doesn't figure neither in RFC 894 nor 826.  So one would have 
> to dig the ethertypes on the Internet find out that type.  The draft 
> spec would be insufficient.
> 
> Another major difference between IPv6 and IPv4 is in the tratment of
>  link-layer multicast.  For example, IPv4 doesn't take into account 
> link-layer multicast, and only cares about broadcast link-layer 
> addresses (0xff...).  IPv6 on the contrary, only considers multicast
>  link-layer addresses (0x33...).  These are aspects that should be 
> accounted for in the IPv-over documents. I don't think mixing them 
> together in one document is simple enough.
> 
> Alex
> 
> [e-mail] wrote:
>> A New Internet-Draft is available from the on-line Internet-Drafts 
>> directories. This draft is a work item of the IP over IEEE 802.16 
>> Networks Working Group of the IETF.
>> 
>> Title		: Transmission of IP over Ethernet over IEEE 802.16
> Networks
>> Author(s)	: H. Jeon, et al. Filename	: 
>> draft-ietf-16ng-ip-over-ethernet-over-802.16-00.txt Pages
> : 17 Date
>> : 2006-12-14  This document describes the behavior of the Ethernet 
>> emulation on top of IEEE 802.16 to efficiently support the 
>> transmission of IPv4 as well as IPv6 packets over IEEE 802.16 radio
>>  links.  Due to resource constraints of radio transmission systems 
>> and the limitations of the IEEE 802.16 MAC layer for the emulation 
>> of Ethernet, the transmission of IP over an emulated LAN on top of 
>> IEEE 802.16 may considerably benefit by adding IP specific support 
>> functions within the Ethernet emulation on top of IEEE 802.16.
>> 
>> 
>> 
>> A URL for this Internet-Draft is:
>> 
> http://www.ietf.org/internet-drafts/draft-ietf-16ng-ip-over-ethernet-ove
>  r-802.16-00.txt
>> 
>> 
>> To remove yourself from the I-D Announcement list, send a message 
>> to [e-mail] 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-16ng-ip-over-ethernet-over-802.16-00.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: [e-mail]. In the body type: "FILE 
>> /internet-drafts/draft-ietf-16ng-ip-over-ethernet-over-802.16-00.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.
>> 
>> 
>> 
> ------------------------------------------------------------------------
> 
> 
>> 
>> 
>> _______________________________________________ I-D-Announce 
>> mailing list [e-mail] 
>> https://www1.ietf.org/mailman/listinfo/i-d-announce
> 
> 
> _______________________________________________ 16NG mailing list 
> [e-mail] https://www1.ietf.org/mailman/listinfo/16ng
> 


_______________________________________________
16NG mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/16ng