Hi, Thank you again Kiran, it works for me. Best, Meral
From: Agrahara Kiran Koushik [mailto:[email protected]] Sent: Wednesday, February 19, 2014 3:34 PM To: Meral Shirazipour Cc: [email protected]; [email protected] Subject: Re: Gen-ART Telechat Call review of draft-ietf-l2vpn-vpls-mib-14 Hi Here is the text we are planning to add in the DESCRIPTION clause for objects which refer to VE ID and have a upper limit of 65535. " The VE ID takes 2 octets in VPLS BGP NLRI according to RFC 4761. Hence we have limited the the range of this object to 65535. " Let me know if this is acceptable? Thanks Kiran On Feb 19, 2014, at 5:06 PM, Meral Shirazipour <[email protected]<mailto:[email protected]>> wrote: I am the assigned Gen-ART reviewer for this draft. For background on Gen-ART, please see the FAQ at < http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq> . Please wait for direction from your document shepherd or AD before posting a new version of the draft. Document: draft-ietf-l2vpn-vpls-mib-14 Reviewer: Meral Shirazipour Review Date: 2013-02-14 IETF LC End Date: 2014-02-14 IESG Telechat date: 2014-02-20 Summary: This draft is ready to be published as Standards Track RFC but I have some editorial comments . Nits/editorial comments: It was noticed that Unsigned32 is used with 16 bit encoding. It would good to mention it in the descriptions like other MIB documents do. Look for "Unsigned32 (1..65535) in the draft : -Offline discussion with one of the authors, a suggestion could be "the number of VPLS Edge devices(VEid) is limited to 65535 in any implementation" Best Regards, Meral --- Meral Shirazipour Ericsson Research www.ericsson.com<http://www.ericsson.com>
_______________________________________________ Gen-art mailing list [email protected] https://www.ietf.org/mailman/listinfo/gen-art
