On (2012-06-25 12:02 -0400), Aaron wrote: > open a bug for FTP support.
HTTP please. Even IOS-XR is missing HTTP. FTP is much more complex protocol, and you'll often run into problems with passive/active and authentication and whatnot. Either on server side, or device itself. IMHO HTTP should be the primary protocol you support for download, for upload sftp/scp. I don't see why, but if HTTP for some reason is impractical in some embedded hardware where TFTP is practical we obviously should standardize new filetransfer protocol for this application * as cheap to implement, or cheaper than TFTP * does not negotiate/swap L4 ports * can transfer high rate at high latency (does not imply TCP, if TCP for some reason is show stopper) * supports large files[0] [0] TFTP standard does not support roll-over of sequence. Only standard way to increase filesize is to increase block size, which does not mean arbitrary filesize. Moreover there are lot of devices which do not support >512B block. IIRC 6500/7600 WLAN controller was one example of hardware to which it is impossible to download image, if you want to do it honoring standards. -- ++ytti _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
