Re: Question about IPv6 Management
"EricLKlein" <[email protected]> Mon, 17 Mar 2003 08:55:48 +0200
| Newsgroups | gmane.ietf.ipv6,gmane.ietf.v6ops,gmane.ietf.eos |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. ------=_NextPart_000_001F_01C2EC63.00F57940 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Thank you. I have been reading: RFC 2452 IP v6 MIB for the TCP RFC 2454 IP v6 MIB for the UDP RFC 2466 MIB for IP v6 ICMP=20 But didn't see anything more detailed. Thanks for the information. Eric ----- Original Message -----=20 From: Wijnen, Bert (Bert)=20 To: EricLKlein ; [email protected] ; [email protected] ; = [email protected]=20 Sent: Monday, March 17, 2003 2:48 AM Subject: RE: Question about IPv6 Management We have been defining a number of things so that IP (or better = Internet) addresses can be represented in an IPversion neutral matter. See for example = RFC3291. We are checking all MIB modules to be IPv4 and IPv6 capable (unless a = module is for one specific IP version).=20 We have defined TCs so that we also have IPv6 transport addresses so = that=20 SNMP can go over IPv6. See RFC3419 Various MIB modules are being reqorked in the IPv6 WG=20 Hope this helps Thanks,Bert=20 -----Original Message----- From: EricLKlein [mailto:[email protected]] Sent: zondag 16 maart 2003 11:19 To: [email protected]; [email protected]; [email protected] Subject: Question about IPv6 Management I appologize, this is being possted to multiple WG's as it seems to = cross areas. Is there any information about the requirment changes in the Network = Management Systems (NMS) or Operations Support Systems (OSS) necesary to = support IPv6? I have looked at the various MIB RFC's and such, but can not find = anything more than you need bigger address support and some SNMPv2 = compliance. This seems too simple to me. Eric ------=_NextPart_000_001F_01C2EC63.00F57940 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Dwindows-1255"> <META content=3D"MSHTML 6.00.2722.900" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT face=3DArial size=3D2>Thank you. I have been = reading:</FONT></DIV> <P class=3DMsoNormal=20 style=3D"MARGIN: 4pt 0cm 0pt 36pt; DIRECTION: ltr; TEXT-INDENT: -36pt; = unicode-bidi: embed; TEXT-ALIGN: left; mso-text-indent-alt: -3.6pt; = mso-list: l0 level1 lfo1; tab-stops: list 50.4pt"><SPAN=20 style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">RFC 2452 IP = v6 MIB for=20 the TCP<?xml:namespace prefix =3D o ns =3D = "urn:schemas-microsoft-com:office:office"=20 /><o:p></o:p></SPAN></P> <P class=3DMsoNormal=20 style=3D"MARGIN: 4pt 0cm 0pt 36pt; DIRECTION: ltr; TEXT-INDENT: -36pt; = unicode-bidi: embed; TEXT-ALIGN: left; mso-text-indent-alt: -3.6pt; = mso-list: l0 level1 lfo1; tab-stops: list 50.4pt"><SPAN=20 style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">RFC 2454 IP = v6 MIB for=20 the UDP<o:p></o:p></SPAN></P> <DIV><SPAN=20 style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; = mso-fareast-font-family: 'Times New Roman'; mso-fareast-language: HE; = mso-ansi-language: EN-US; mso-bidi-language: HE">RFC=20 2466 MIB for IP v6 ICMP </SPAN></DIV> <DIV><SPAN=20 style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; = mso-fareast-font-family: 'Times New Roman'; mso-fareast-language: HE; = mso-ansi-language: EN-US; mso-bidi-language: HE"></SPAN> </DIV> <DIV><SPAN=20 style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; = mso-fareast-font-family: 'Times New Roman'; mso-fareast-language: HE; = mso-ansi-language: EN-US; mso-bidi-language: HE">But=20 didn't see anything more detailed. Thanks for the = information.</SPAN></DIV> <DIV><SPAN=20 style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; = mso-fareast-font-family: 'Times New Roman'; mso-fareast-language: HE; = mso-ansi-language: EN-US; mso-bidi-language: HE">Eric</SPAN></DIV> <BLOCKQUOTE dir=3Dltr=20 style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; = BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px"> <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV> <DIV=20 style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: = black"><B>From:</B>=20 <A [email protected] = href=3D"mailto:[email protected]">Wijnen, Bert=20 (Bert)</A> </DIV> <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A [email protected]=20 href=3D"mailto:[email protected]">EricLKlein</A> ; <A = [email protected]=20 href=3D"mailto:[email protected]">[email protected]</A> ; <A=20 [email protected] = href=3D"mailto:[email protected]">[email protected]</A> ;=20 <A [email protected]=20 href=3D"mailto:[email protected]">[email protected]</A> = </DIV> <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Monday, March 17, 2003 = 2:48=20 AM</DIV> <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> RE: Question about = IPv6=20 Management</DIV> <DIV><BR></DIV> <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN = class=3D337404315-16032003>We=20 have been defining a number of things so that IP (or better Internet)=20 addresses</SPAN></FONT></DIV> <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN = class=3D337404315-16032003>can=20 be represented in an IPversion neutral matter. See for example=20 RFC3291.</SPAN></FONT></DIV> <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20 class=3D337404315-16032003></SPAN></FONT> </DIV> <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN = class=3D337404315-16032003>We=20 are checking all MIB modules to be IPv4 and IPv6 capable (unless a=20 module</SPAN></FONT></DIV> <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN = class=3D337404315-16032003>is=20 for one specific IP version). </SPAN></FONT></DIV> <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20 class=3D337404315-16032003></SPAN></FONT> </DIV> <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN = class=3D337404315-16032003>We=20 have defined TCs so that we also have IPv6 transport addresses so that = </SPAN></FONT></DIV> <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN = class=3D337404315-16032003>SNMP=20 can go over IPv6. See RFC3419</SPAN></FONT></DIV> <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20 class=3D337404315-16032003></SPAN></FONT> </DIV> <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20 class=3D337404315-16032003>Various MIB modules are being reqorked in = the IPv6 WG=20 </SPAN></FONT></DIV> <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20 class=3D337404315-16032003></SPAN></FONT> </DIV> <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN = class=3D337404315-16032003>Hope=20 this helps</SPAN></FONT></DIV> <P><FONT size=3D2>Thanks,</FONT><FONT size=3D2>Bert </FONT></P> <BLOCKQUOTE=20 style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px = solid; MARGIN-RIGHT: 0px"> <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT = face=3DTahoma=20 size=3D2>-----Original Message-----<BR><B>From:</B> EricLKlein=20 [mailto:[email protected]]<BR><B>Sent:</B> zondag 16 maart = 2003=20 11:19<BR><B>To:</B> [email protected]; [email protected];=20 [email protected]<BR><B>Subject:</B> Question about IPv6=20 Management<BR><BR></DIV></FONT> <DIV><FONT face=3DArial size=3D2>I appologize, this is being possted = to multiple=20 WG's as it seems to cross areas.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Is there any information about the = requirment=20 changes in the Network Management Systems (NMS) or <FONT = size=3D3>Operations=20 Support Systems (OSS) necesary to support = IPv6?</FONT></FONT></DIV> <DIV> </DIV> <DIV><FONT face=3DArial>I have looked at the various MIB RFC's = and such,=20 but can not find anything more than you need bigger address support = and some=20 SNMPv2 compliance.</FONT></DIV> <DIV> </DIV> <DIV><FONT face=3DArial>This seems too simple to me.</FONT></DIV> <DIV> </DIV> <DIV> <FONT face=3DArial=20 size=3D2>Eric</FONT></DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML> ------=_NextPart_000_001F_01C2EC63.00F57940-- -------------------------------------------------------------------- IETF IPng Working Group Mailing List IPng Home Page: http://playground.sun.com/ipng FTP archive: ftp://playground.sun.com/pub/ipng Direct all administrative requests to [email protected] --------------------------------------------------------------------