IPv6 RFC's

• RFC1752 - The Recommendation for the IP Next Generation Protocol
• RFC2460 - Internet Protocol, Version 6 (IPv6) Specifications (Obsoletes RFC1883)
Transition
• RFC4213 - Basic Transition Mechanisms for IPv6 Hosts and Routers
• RFC4942 - IPv6 Transition/Coexistence Security Considerations
• RFC4038 - Application Aspects of IPv6 Transition
• RFC4192 - Procedures for Renumbering an IPv6 Network without a Flag Day See Things to think about when renumbering an IPv6 network (draft chown)
• RFC4380 - Teredo: Tunneling IPv6 over UDP through NATs
• RFC3056 - Connection of IPv6 Domains via IPv4 Clouds (6to4 tunnel)
• RFC2743 - Generic Packet Tunneling in IPv6 Specification (See RFC1701 - GRE)
ISP
• RFC4029 - Scenarios and Analysis for Introducing IPv6 into ISP Networks
• RFC2185 - Routing Aspects Of IPv6 Transition
IPV6 Addressing space
• RFC4291 - IP Version 6 Addressing Architecture (Obsoletes RFC3513)
• RFC3769 - Requirements for IPv6 Prefix Delegation
• RFC1744 - Observations on the Management of the Internet Address Space
• RFC3587 - IPv6 Global Unicast Address Format
• RFC4193 - Unique Local IPv6 Unicast Addresses
• RFC3879 - Deprecating Site Local Addresses
• RFC4862 - IPv6 Stateless Address Autoconfiguration
• RFC3484 - Default Address Selection for Internet Protocol version 6 (IPv6)
• RFC3633 - IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6
• RFC4861 - Neighbor Discovery for IP version 6 (IPv6)
• RFC3971 - SEcure Neighbor Discovery (SEND)
• RFC4941 - Privacy Extensions for Stateless Address Autoconfiguration in IPv6 (RFC3041)
• RFC3972 - Cryptographically Generated Addresses (CGA) Allocation
• RFC3177 - IAB/IESG Recommendations on IPv6 Address Allocations to Sites
• RFC1887 - An Architecture for IPv6 Unicast Address Allocation
• RFC1881 - IPv6 Address Allocation Management
• RFC4548 - Internet Code Point (ICP) Assignments for NSAP Addresses
• RFC1981 - Path MTU Discovery for IP version 6
• RFC4443 - Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification
• RFC3596 - DNS? Extensions to Support IP Version 6
• RFC2464 - Transmission of IPv6 Packets over Ethernet Networks
• RFC2675 - IPv6 Jumbograms
Security
• RFC4864 - Local Network Protection for IPv6
• RFC4301 - Security Architecture for the Internet Protocol
• RFC4302 - IP Authentication Header
• RFC4835 - Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH)
• RFC1828 - IP Authentication using Keyed MD5
• RFC1829 - Encapsulation, algorithme CBC du DES (Cypher Block Chaining)
• RFC1851 - Triple transformation par le DES
• RFC1852 - Authentification IP par clés SHA
Other
• RFC3053 - IPv6 Tunnel Broker

Blocking based on file size in Bluecoat Proxy SG

For blocking the download based on file size, you would have to apply that under the Visual Policy Manager. It would be under the Web Access Layer and under Destination. Click set and select Response Header. Set the Header Name to Content-Length and add the Header Regex below according to the file size. Note that those regex below will block the file size specified and above.

500kb :

[0-9]{7,12}|[5-9][0-9]{4}

1 MB :

[0-9]{8,12}|[1-9][0-9]{6}

2 MB :

[0-9]{8,12}|[2-9][0-9]{6}

3 MB :

[0-9]{8,12}|[3-9][0-9]{6}

5 MB :

[0-9]{8,12}|[5-9][0-9]{6}

10 MB :

[0-9]{9,12}|[1-9][0-9]{8}

20 MB :

[0-9]{9,12}|[2-9][0-9]{8}

50 MB :

[0-9]{9,12}|[5-9][0-9]{8}

100 MB :

[0-9]{10,12}|[1-9][0-9]{10}

Delete the SGOS image from ProxySG

You can delete the SGOS image/installed-system from ProxySG via the command line interface (CLI). Here is an example of how to delete a version of SGOS that is currently installed on your system. Please note that it is not necessary to delete an image before performing an upgrade or installing a new version of SGOS.
SGOS>en
Enable Password:
SGOS#config t
Enter configuration commands, one per line. End with CTRL-Z.
SGOS#(config)installed-systems
SGOS#(config installed-systems)view
ProxySG Appliance Systems
1. Version: SGOS 5.4.2.2, Release ID: 41580
Friday August 7 2009 03:29:40 UTC,
Attributes: Locked, FIPS capable
Boot Status: Last boot succeeded, Last Successful Boot: Monday September 7 2
009 12:52:52 UTC
2. Version: SGOS 5.4.1.12, Release ID: 40038
Wednesday June 17 2009 02:35:14 UTC,
Attributes: FIPS capable
Boot Status: Last boot succeeded, Last Successful Boot: Wednesday August 26
2009 23:58:22 UTC
3. Version: SGOS 5.3.3.1, Release ID: 39156
Thursday April 30 2009 00:30:57 UTC,
Attributes: FIPS capable
Boot Status: Last boot succeeded, Last Successful Boot: Thursday August 27 2
009 16:45:48 UTC
4. Version: SGOS 4.2.8.6, Release ID: 35252
Wednesday July 16 2008 22:53:55 UTC,
Attributes: None
Boot Status: Last boot succeeded, Last Successful Boot: Wednesday August 26
2009 22:46:06 UTC
5. Version: SGOS 4.2.7.1, Release ID: 32941
Thursday February 28 2008 22:26:10 UTC,
Attributes: None
Boot Status: Last boot succeeded, Last Successful Boot: Wednesday September
2 2009 14:41:31 UTC
Default system to run on next hardware restart: 1
System to replace next: 5
Current running system: 1
Enforce signed: Disabled
SGOS#(config installed-systems)delete 5
Are you sure you want to delete system 5? (y or n)y

ok
SGOS#(config installed-systems)view
ProxySG Appliance Systems
1. Version: SGOS 5.4.2.2, Release ID: 41580
Friday August 7 2009 03:29:40 UTC,
Attributes: Locked, FIPS capable
Boot Status: Last boot succeeded, Last Successful Boot: Monday September 7 2
009 12:52:52 UTC
2. Version: SGOS 5.4.1.12, Release ID: 40038
Wednesday June 17 2009 02:35:14 UTC,
Attributes: FIPS capable
Boot Status: Last boot succeeded, Last Successful Boot: Wednesday August 26
2009 23:58:22 UTC
3. Version: SGOS 5.3.3.1, Release ID: 39156
Thursday April 30 2009 00:30:57 UTC,
Attributes: FIPS capable
Boot Status: Last boot succeeded, Last Successful Boot: Thursday August 27 2
009 16:45:48 UTC
4. Version: SGOS 4.2.8.6, Release ID: 35252
Wednesday July 16 2008 22:53:55 UTC,
Attributes: None
Boot Status: Last boot succeeded, Last Successful Boot: Wednesday August 26
2009 22:46:06 UTC
5. Version: N/A, Release ID: N/A ( EMPTY )
No Timestamp,
Attributes: None
Boot Status: Unknown, Last Successful Boot: Unknown
Default system to run on next hardware restart: 1
System to replace next: 5
Current running system: 1
Enforce signed: Disabled
SGOS#(config installed-systems)

Configuring WCCP on the Router

Step 1. Ensure that the router is running
WCCP Version 2 (this is the default)

Router>enable
Router#configure terminal
Router(config)#ip wccp version 2

Step 2 Enable WCCP and specify the
service group ID or keyword.

Router(config)#ip wccp 90

Step 3 Save the configuration startup-config

Router(config)#copy running-config

Load Balancing Weight on Bluecoat Proxy SG

ProxySG appliances with higher weight values receive a higher

proportion of the redirected traffic than ProxySG appliances with lower weight values. For example,

suppose you have assigned the following weight values: ProxySG1=100, ProxySG2=100, and ProxySG3=50

respectively. The total weight value is 250, and so ProxySG1 and ProxySG2 will each receive 2/5 of the

traffic (100/250) and ProxySG3 will receive 1/5 of the traffic (50/250).